Enterprise
Roles and Permissions
Roles define who can manage organizations, projects, keys, usage visibility, billing, and security settings.
Roles define who can manage organizations, projects, keys, usage visibility, billing, and security settings.
Current role model
| Role | Typical owner | Main responsibility |
|---|---|---|
| Admin | Platform or IT lead | Organization-wide control |
| Project Owner | Team or product lead | Project-level operations |
| Member | Developer or builder | Day-to-day API usage |
| Finance | Billing owner | Billing and invoices |
Practical access split
| Area | Admin | Project Owner | Member | Finance |
|---|---|---|---|---|
| organization settings | full | none | none | none |
| member management | full | project-scoped | none | none |
| key management | full | project-scoped | own resources only | none |
| usage visibility | full | project-scoped | own or assigned context | none |
| billing and invoices | full | none | none | finance workflows |
Project scoping matters
Project Owner and Member permissions are limited by project context:
- Project Owner manages people, keys, and usage inside the current project
- Member works only with their own or assigned project resources
Fine-grained permissions
The table above is an outcome-level map. Enterprise accounts may use additional fine-grained controls depending on rollout stage and account configuration.