Team Management
A workspace can have multiple team members, each with a role that controls what they're able to see and do across every project in that workspace.
Roles
Roles form a strict hierarchy, from highest to lowest privilege:
| Role | Access |
|---|---|
owner | Full control over the workspace, including irreversible workspace-level actions that only the workspace's creator or owner should be able to take. |
admin | Can manage most settings and team members, but not owner-only actions. |
member | Day-to-day contributor access — can create and edit projects and see everything relevant to their work, but can't manage admin-level settings. |
viewer | Read-only. Can see dashboards and configuration, but can't change anything. |
owner > admin > member > viewer — each role includes everything the roles below it can do.
Inviting a teammate
- Open your workspace's team management screen in the dashboard.
- Enter the teammate's email address.
- Pick a role for them.
- Send the invite. They'll receive an email invitation to join the workspace at that role.
Changing or removing access
From the same team management screen, you can change an existing teammate's role or remove their access to the workspace entirely.
Recommended practice
Default new teammates to viewer or member — only grant admin or owner to people who actually need to manage API keys, billing, or team membership. Fewer people with elevated access means less exposure if a single account is ever compromised. See Security best practices for a broader checklist.
Next steps
- Projects and API keys — what
member-and-above access lets you manage. - Human escalation ops — role expectations for operators working the escalation queue.
- Security best practices — least-privilege recommendations across the whole workspace.