Guides
Organizations
Teams, roles, invitations, and why another organization's data answers 404.
Everything a customer creates belongs to an organization. People join by invitation and hold one of three roles:
| Role | Can |
|---|---|
| Member | Work with projects and files |
| Admin | Also manage members, billing, API keys and single sign-on |
| Owner | Everything, including deleting the organization |
Scoping
Every query names the organization it may read. A request for another organization's project gets the same 404 as one for a project that does not exist, so ids cannot be probed. Membership is checked on every request: leaving an organization ends access at once.
API keys
Keys are pinned to one organization and carry scopes such as projects:read. Send one as the X-API-Key header. Managing keys is never delegated to a key.