Roles, members, and teams
Organization roles, member invitations, permissions, and teams.
An organization is the boundary between workspaces; roles decide what each member may do inside it. Manage members, invitations, and teams from the Team page.
Roles
| Role | May |
|---|---|
| Viewer | Read everything in the organization. |
| Member | Everything a viewer can, plus create and change monitors, incidents, maintenance, status pages, and alerts. |
| Admin | Everything a member can, plus manage members, teams, API keys, and organization settings. |
| Owner | Everything an admin can, plus transfer ownership and delete the organization. |
The Team page displays the admin role as Administrator.
Two personal actions work for every role, including viewers: editing your own profile, and switching which organization you are viewing.
An API key acts with the role of the user who created it, on top of the key's own scopes. Lowering someone's role therefore lowers their keys too.
Guard rails
- An admin cannot create an owner; granting ownership is the owner's decision alone.
- Nobody can change or remove a member who outranks them.
- The last owner cannot be demoted or removed, which would leave the organization with nobody able to administer it. Anyone else may leave at any time.
Invite people
An admin invites people from Team → Invite people with an email address and a role. The invitation is emailed as a link that lasts seven days. The link is bound to the invited address: accepting it requires the signed-in account's own email to match.
Invitations are sent through the instance mail relay; the Team page shows a banner when no relay is configured. Re-inviting the same address replaces the pending invitation rather than creating a second one. Pending invitations can be revoked at any time, and who has been invited is admin-only information.
Invited people follow the link to sign in or create a password account, then join the organization with the invited role. See Getting started for the sign-in flow.
Teams
A team groups people within one organization. Incidents can be assigned to a team, and comments can @mention its members.
Create teams from Team → New team with a unique name, a description, and members. Only people who are already members of the organization can be added, so a team can never grant someone entry. Deleting a team removes it from incident assignment; its members keep their access and their roles.
Audit
Every role change, removal, invitation, revocation, acceptance, and team change is written to the audit log with the actor and the organization.