Files and cloud drive
Keep input materials and finished work in cloud drive. Choose a location based on who needs access and how the files will be used.
On this page
Choose a location
| Location | Suitable for | Access |
|---|---|---|
| My drive | Personal resources and templates | Current user's permissions |
| Session drive | Task attachments and deliverables | Session-related permissions |
| Channel drive | Materials for a shared discussion | Channel access and permissions |
| Organization drive | Team resources | Organization and enterprise permissions |
| Organization public drive | Intentionally public assets | Public file links |
Swipe sideways to see more of a wide table.
Agents also have related resource and skill directories. You do not need to memorize technical paths: ask where a file is saved and open it through the drive interface.
Give files to an assistant
Drag a local file into the composer, wait for uploading to finish, and send it with your instructions. Attachments are saved to the target session or channel drive when sent.
Dragging a cloud file into a draft does not immediately copy it into the conversation. Cancelling the draft does not submit the attachment.
A single chat attachment upload supports up to 512 MiB. An interrupted upload must restart. Smaller, relevant excerpts are often easier to process accurately.
Preview, download, and organize
Open file cards or browse the drive. Supported previews vary by file type; download a file and open it in the appropriate software if no preview is available. Video previews support playback and seeking.
Create folders, rename files, or copy and move them. Dragging a conversation attachment into an open drive folder copies it on drop and retains the source.
Separate source files, working drafts, and final results. For batch changes, ask the assistant to preserve originals and test a few samples first.
Drive versus sandbox
The drive is a filing cabinet. The sandbox is the assistant's cloud computer for tools, installed software, and temporary work. A sandbox file is not automatically a drive file.
Save the final report and related spreadsheets to this session's cloud drive. List each file, its purpose, and a link I can open. Do not leave the only copy in a temporary working directory.
Archiving destroys the sandbox but preserves session-drive files. Forking creates an empty new drive. Moving or deleting a source file may affect existing references.
When a file will not open
Check the organization, file location, permissions, and whether it still exists. A share link exposes only its permitted content, not every drive owned by the sender.
If a preview fails, try downloading. If the assistant supplied only a temporary local path, ask it to copy the result to cloud drive and provide an accessible link.