roles & permissions
Each member holds one role per org. A role governs what they can change.
| role | what they can do |
|---|---|
| owner | full access. Can delete the org and transfer ownership. One per org. |
| admin | manage members, channels, monitors, and rules. Can't delete the org or transfer ownership. |
| member | view monitors and incidents; manage their own notification preferences. |
| viewer | read-only. |
Whoever creates an org is its owner. Roles are assigned when inviting a
member and can be changed later from the /team members tab.
how roles gate the UI
The app gates actions by your role in the active org — buttons for things you can't do are hidden or disabled rather than failing on submit. The backend enforces the same checks on every API call, so a role limit holds regardless of which surface (UI, CLI, MCP) you reach the API through.
note
Personal access tokens inherit your role in each org — a token can do exactly what you can, no more. There's no separate per-token scope system today.
stack-as-code roles
The GitOps endpoints follow the same model:
apply(which mutates) is admin/owner only — members and viewers get a 403.dump(read-only export) is available to any member.