Permissions on files and folders
Permissions live in storage, not separately in every product
What it gives you
Permissions are granted on a file or a folder and describe a subject and a set of actions: read, edit, delete, share. The subject can be a user, a department, a project or a public link. An external product, and an internal one alike, receives not the whole storage but permissions on specific objects and folders, in a model close to OAuth.
How it works
- Permission subjects: user, department, project, public access
- Integration permissions limit what a product may reach and bind to
- Hiding an attachment is presentation, not an access permission
- Unlinking is confirmed by a one time token signed by the product
Limitations
- An integration sees only the objects and folders the owner granted it, not the whole storage
- Hiding a file from listings does not replace permissions: only permissions can close a file
Which plan includes it
Platform
The feature is included in this plan and in every plan above it.
Compare plansFrequently asked questions
Who can be granted permissions on a folder?
A user, a department, a project or anyone with a public link. Each subject gets a set of actions: read, edit, delete and share.
How do I limit what an external integration can access?
The integration is registered in the storage and receives permissions only on the objects and folders the owner allowed. A3 products connect under the same rules.
Can products grant access to files bypassing the storage?
No. Products add their own logic on top, but the storage decides who may access an object. A3 products and external integrations use one and the same contract.
