Organizations and Teams
Organizations and teams let you share API keys with collaborators. Orgs group users together. Teams within an org control which keys each group of users can access.
Organizations
An organization is a shared workspace for API keys and users.
Roles
| Role | Permissions |
|---|---|
| Owner | Full access: all org keys, members, and teams |
| Admin | Full access: all org keys and teams |
| Member | Access only through team assignments |
What Org Members See
Owners and admins see all API keys created under the organization. Members see only keys assigned to teams they belong to.
Teams
Teams are groups within an organization. Each org starts with a default team that automatically includes new org keys.
Team Roles
| Role | Permissions |
|---|---|
| Owner | Manage team members and key assignments |
| Admin | Manage key assignments |
| Member | Access keys at the assigned permission level |
Key Permissions
When a key is assigned to a team, it gets a permission level:
| Permission | View key | Edit key settings |
|---|---|---|
| admin | Yes | Yes |
| write | Yes | Yes |
| read | Yes | No |
How Key Visibility Works
You can see an API key if any of these conditions apply:
- You created it (it's your personal key).
- You're an owner or admin of the org the key belongs to.
- You're a member of a team the key is assigned to.
Related
- Managing API Keys: Creating and configuring keys
- Dashboard Overview: All dashboard sections