Some teams keep exports, shared reports, and plant backups on a shared drive or in folders that are hard to find later. In Threaded, when file storage is turned on, your organization has one place for those files. You browse them in Admin, upload and download there, or use the same files from threaded storage on your computer or in CI.
This is not the Media library. Media holds images and documents you attach to work instructions and actions. File storage is for your organization’s own files, separate from Media.
#What it is
- File storage. Shared storage for your organization. Paths look like folders and file names, such as
reports/2026-10/line3.csv, relative to your organization’s files root. - File Storage page. The in-app browser for that storage at Admin › File Storage. The page title is File Storage.
- Short-lived access. In the app, your ability to list, download, or upload in the browser lasts about 15 minutes. When it expires, refresh or try the action again and Threaded grants a new session. Download and upload links from the API also expire after about 15 minutes.
- CLI storage.
threaded storage list,get, andputreach the same files through the API.
#Rules
- Your organization needs file storage turned on. See Feature Access and Billing.
- You must be a signed-in active organization member to use file storage. Non-members are refused with You must be an active organization member to use file storage. or You must be an active organization member to use Storage Browser.
- When file storage is not turned on for your organization, the File Storage tab in Admin still appears. The page shows File Storage is off and tells you to contact Threaded support to turn it on. Until it is on, API calls can return 403 File storage is not enabled for this organization. Contact Threaded support to turn it on. or The Storage Browser feature is not enabled for this organization.
- When the feature is on but file storage is not set up yet for your organization, the page shows Files are not configured for this organization. API calls can return 404 Storage Browser is not configured for this organization. or 404 File storage is not set up for this organization. Contact Threaded support to set it up.
- Viewers can list folders and download. They cannot upload. Upload attempts can return 403 Your access to this organization does not let you upload files to file storage.
- Editors and owners can list, download, and upload. Owners can also delete files in the in-app browser. Nobody can delete through
threaded storageyet. - Operators and members with no access cannot use file storage. If they open the page while the feature is on, they have no read or write access in the browser.
- API tokens can list and download with
org:read, and upload withorg:write. They cannot use the in-app browser sign-in flow (Service tokens cannot access this endpoint.). They cannot delete files. - Uploading replaces a file already at the same path. There is no versioning.
- Files up to 64 MiB upload in one step. Larger files upload in parts (still up to 5 TiB total). The CLI handles part size automatically.
- Paths must be relative: no
.or..segments, no leading/, no*,?,$, or\, no control characters, no empty path segments (//), no folder name that starts or ends with a dot, and no folder or file name that starts or ends with whitespace.
#In the app
#Open File Storage
Open the Admin gear and choose File Storage.
The page title is File Storage. While the page loads, a progress indicator appears. When file storage is turned on and set up, the browser shows folders and files for your organization. When it is not turned on, the page shows File Storage is off instead of the browser.
#Browse, upload, and download
Use the browser to open folders, upload files, download files, and (if you are an owner) delete files. What you can do matches your organization role: viewers read only; editors and owners can write; only owners can delete.
If setup is incomplete after load, the page shows Files are not configured for this organization.
Signing out of Threaded ends your session in the browser; open File Storage again after you sign back in.
#Troubleshooting
File Storage is off. File storage is not turned on for your organization. The File Storage tab in Admin still opens, but the page shows File Storage is off instead of the browser. Contact Threaded support to turn it on. API calls return the messages above until the feature is on.
Files are not configured for this organization. Contact Threaded support to set up file storage for your organization. Until then, the browser cannot list files.
I can see the page but cannot upload or download. Your role may be Operator, no access, or Viewer (for upload). Ask an owner to check your role under Admin › People and roles. See Membership and Sharing.
A download or upload stopped working after a few minutes. Access in the browser and download or upload links last about 15 minutes. Refresh the folder or run the action again.
File storage is unavailable right now. Try again shortly. Threaded could not reach file storage. Retry. If it persists, contact support.
The file in storage does not match what was uploaded. Upload it again. An upload did not finish cleanly over an existing file. Run the upload again.
No file at that path. The path does not exist, or you cannot access it. Check spelling and folder names.
#From the CLI or API
Use threaded storage on your computer or in CI with a personal login or an API token. Hosted MCP scripts can call the storage API as the signed-in person; threaded storage get and put need a local filesystem and are not for the hosted runner.
#Commands
threaded storage list [path] [--recursive] [--json] [--cursor <cursor>] [--limit <n>]
threaded storage get <path> [-o <dest>] [--recursive] [--no-progress]
threaded storage put <local> [remote-folder] [--name <file-name>] [--content-type <type>]
Paths are relative to the organization’s files root, like reports/2026-10/line3.csv.
Examples:
threaded storage list
threaded storage list reports/2026-10 --recursive --json
threaded storage get reports/2026-10/line3.csv -o ./data/
threaded storage get reports --recursive -o ./reports
threaded storage put ./line3.csv reports/2026-10
More detail: threaded instructions show storage.
#API operations
In-app browser (signed-in person only):
GET /api/v1/organizations/{organization_uuid}/storage-browser/config/— what your role may do in the browser (get,list,write,delete).POST /api/v1/organizations/{organization_uuid}/storage-browser/credentials/— short-lived credentials to open a folder in the browser.
Storage (people, API tokens with the right scopes, or a hosted script acting as its user):
GET /api/v2/storage/organizations/{organization_uuid}/files/— list a folder (path, optionalrecursive,cursor,limitup to 1000).POST .../files/download/— bodypath; returns a download URL and file metadata (links expire after about 15 minutes).POST .../files/upload/— start upload (path,size,content_type); large files use a multipart flow (upload/parts,upload/complete,upload/abort).
#Common errors
- 403 File storage is not enabled for this organization. Contact Threaded support to turn it on. — feature off.
- 403 Your access to this organization does not let you read file storage. or … upload files to file storage. — role or token scope.
- 403 This service token belongs to another organization. — wrong
--organizationfor the token. - 403 Service tokens cannot access this endpoint. — API token used an in-app-only browser endpoint.
- 404 File storage is not set up for this organization. Contact Threaded support to set it up. — file storage not configured.
- 404 No file at that path. — missing file.
- 409 The file in storage does not match what was uploaded. Upload it again. — incomplete upload over an existing file.
- 503 Storage Browser credentials are unavailable right now. — browser access temporarily unavailable.
- 502 File storage is unavailable right now. Try again shortly. — file storage temporarily unavailable.