documentation / operate
Organizations and roles
Organize your people without mixing file access and billing authority.
| Role | Access |
|---|---|
| Owner | Every organization, application, identity, and billing control |
| Admin | Application management, and inviting or removing developers and viewers |
| Developer | Application files, configuration, and API keys |
| Billing | Usage, plans, payment methods, and invoices |
| Viewer | Application and file metadata, with no file contents and no changes |
Only owners can grant privileged roles. Admins can invite developers and viewers. Only the verified email address an invitation was sent to can accept it, and an expired or revoked invitation grants nothing.
An organization always keeps at least one owner. Make someone else an owner before you delete the last owner's account.
The owners of both organizations must accept an application transfer. A paid application moves at the end of its billing period. A Free application moves only if the destination's Free pool has room. The source organization owns the application until it moves and keeps any earlier debt.
The application's API keys rotate at transfer, so update UPLOADFILE_TOKEN wherever you use it afterwards.