Roles and permissions

What an owner, admin, member, and viewer can each do in a project.

This page lists what each role can do in a project. Roles are per project. The owner is the account that created the project and cannot be changed. Admin, Member, and Viewer are assigned when someone is invited and can be changed on the Team page.

#The roles

Role	In one line
Owner	Everything, including renaming and deleting the project. Their plan governs it.
Admin	Everything an owner can do except rename or delete the project.
Member	Create and manage monitors. No access to channels, team, or status page settings.
Viewer	Read everything. Change nothing.

#Permission matrix

Action	Owner	Admin	Member	Viewer
See monitors, incidents, channels, settings, and the roster	Yes	Yes	Yes	Yes
Create, edit, pause, and delete monitors	Yes	Yes	Yes	No
Add, edit, test, and delete notification channels	Yes	Yes	No	No
Change notification settings and the incident policy	Yes	Yes	No	No
Declare incidents, post updates, write postmortems	Yes	Yes	No	No
Acknowledge an incident	Yes	Yes	Yes	No
Schedule and delete maintenance windows	Yes	Yes	No	No
Create, edit, and delete the status page	Yes	Yes	No	No
Connect or disconnect a custom domain	Yes	Yes	No	No
Invite, change roles, revoke invites, remove members	Yes	Yes	No	No
Edit on-call escalation	Yes	Yes	No	No
Create API keys for the project	Yes	Yes	Yes	No
Read the project's audit log	Yes	Yes	No	No
Rename or delete the project	Yes	No	No	No
Leave the project	No	Yes	Yes	Yes

An API key acts with the role of the person who created it, inside its project only. A viewer's key can read but not write. Each person sees and revokes only the keys they created.

#Account-level actions

Billing, the account's own audit log, password changes, and account deletion belong to the account, not to a project. Every account manages its own, whatever its role in other people's projects.

#What's next?

Invite teammates: how a role is assigned and changed.
REST API: how keys inherit a role.