# File associations, references, and temporary reads

Ordinary Workspace uploads create file records and stored objects without automatically associating volumes. Private Catalog uploads automatically create a private-volume association and set the reference count to 1. Lists read volume association locations; an unassociated file does not automatically appear in location lists after ordinary upload.

Upload persists metadata before writing the object, with another transaction for private-volume publication. Failure does not guarantee rollback of earlier stages, and this protocol provides no idempotency request key. A client timeout does not mean nothing was created. Retain returned identifiers and check actual state. Actual privileges and reference counts determine cleanup.

Workspace file DELETE requires zero references; built-in samples are protected. Use the existing volume-reference removal API. Positive reference counts or concurrent cleanup failure may reject deletion. Confirm through HTTP204 and subsequent reads. External-file cleanup removes MOI metadata only, not source connector objects.

Issuing model links requires configured BaseURL, key, and TTL. url uses signed capability validation, not the external caller's product identity. Use expires_at for expiry. Content reads uniformly return 404 for unreadable, invalid, expired, or empty files. Link reads do not perform model inference.

Preview and download select different content types. HTML/HTM/SVG previews are attachments; Office conversion depends on configuration. Raw downloads may return only a prefix, so the successful returned length is not the original file length.
