Drive concepts

Drive is workspace-scoped file storage and the canonical place every Destesi product registers the artifacts it creates. This page explains the model so you know where your files live and why.

What Drive is

A simple, browsable file library, scoped to one workspace:

• Folders form a tree. Each folder belongs to one workspace and can contain files and sub-folders.
• Files carry a name, a MIME type, a size, and an upload attribution. They live inside a folder (or at the workspace root).
• Everything is private to the workspace. Drive never leaks the existence of one workspace’s files to another — a file you can’t see returns “not found”, not “forbidden”.

Names are unique within a folder (case-insensitive), so you can’t end up with two files called report.pdf side by side.

The one-library model

Drive’s defining idea: every artifact any product creates is registered in Drive. When Chat generates an image, Studio renders a video, or Text-to-Speech synthesizes a voiceover, the result is saved into Drive automatically — into a clearly-named per-product folder (Chat generated, Studio generated, TTS generated, ImageGen generated). Video that Studio renders lands in Render generated, named after the rendering step that produced it.

That means you have one place to look for everything the suite produces, instead of a separate silo inside each product. The producing product owns the generation; Drive owns the storage.

Note

Producing products write into Drive over a secure service-to-service path — they stream the bytes straight in, attributed to the product (for example service:studio-agent), so the artifact shows up in your workspace the moment it’s ready.

System folders

Some products store private working files — for example a source file a render was built from — that you don’t need to see in your library. These land in hidden system folders and are filtered out of the normal listing by default, so your view stays clean. They still belong to your workspace and count toward storage; they’re just kept out of the way.

Soft delete

Deleting a file or folder is a soft delete: the row is marked deleted and disappears from listings, and the name is freed up so you can immediately reuse it. This keeps “rename after delete” and “re-upload the same filename” working without surprises.

How Drive fits the wider suite

WorkspacesThe tenant that owns every folder and file in Drive.

Accounts & SSOOne login; open Drive from the launcher in any product.

ConnectWhere third-party credentials live for the rest of the suite.

DriveThe suite-wide artifact library, in one sentence.

• Accounts & SSO — you sign in once; your session follows you into Drive with no second login.
• Workspaces — switching your active workspace switches which library you see; folders and files never cross workspace boundaries.
• Producing products (Chat, Studio, Text-to-Speech, Image generation) — register their outputs in Drive automatically.

Authentication models

Drive accepts three kinds of caller, all workspace-scoped:

• Browser session — the drive_session cookie set after single sign-on. This is what the Drive web app uses.
• Drive API keys — drive_-prefixed bearer tokens you mint in the web app for scripts and automation. Scoped to the workspace they were created in.
• Personal access tokens — identity-issued idn_pat_ tokens, sent with an X-Destesi-Workspace header to select which workspace the call targets.

See the reference for the exact request shapes.