Files and storage quota
A reference for the Storage page: what it holds, what it does not show you, and what fills up your allowance.
What Storage is for
Storage holds files belonging to your organization: installers, scripts, images, configuration, anything a workflow step needs to fetch or that you want kept alongside your deployments.
Select Storage in the sidebar. The page is titled Storage and organizes files into folders you create.
Working with files
| Action | Where |
|---|---|
| Upload | Upload Files, or drag files onto the page |
| Create a folder | New Folder |
| Move between folders | Select a folder to open it, and use the breadcrumb trail to go back |
| Search | The search box, across the current view |
| Download, rename, delete | The actions menu on any row |
| Act on several at once | Select multiple rows for bulk actions |
Your allowance
A bar at the bottom of the page shows how much you have used against your plan's allowance, with the amount remaining beside it.
| Usage | Bar |
|---|---|
| Up to 75% | Green |
| Above 75% | Yellow |
| Above 90% | Red |
| Unlimited allowance | Green, with Unlimited in place of a remaining figure |
Uploads are refused once the allowance is reached. See Plan limits and usage.
Files you cannot see
This is the part worth knowing before your allowance fills up.
Files come from two places. Uploaded files arrive through this page and are listed here. Run artifacts are produced by deployments, when a workflow step uploads output from a device.
Run artifacts count against your storage allowance, and the file browser does not show them. Storage lists uploaded files only.
If your usage bar is fuller than the files in front of you can account for, the difference is run artifacts. Deleting things here will not recover that space.
Artifacts belong to the run that produced them. To find them, open Deployments, select the run, and look at its Artifacts section. See Deployment states.
Who can do what
| Viewer, User | Admin, Owner | |
|---|---|---|
| Browse, search, and download files | Yes | Yes |
| Upload, rename, delete, create folders | No | Yes |
Changing what is in Storage is an administrator's job. Note that this is a higher bar than building workflows, which the User role can do. Someone who can create a workflow that fetches a file cannot necessarily put that file there, so the two often need to happen together.
Storage needs an active subscription, like the rest of the app.
Related
- Plan limits and usage for what your plan allows.
- Deployment states for finding run artifacts.