Who can reach what
Team & roles
A status page is usually run by more than one person, and the person who posts incidents at 3am is rarely the person who owns the billing relationship.
Dashboard → Settings → Team. The list shows everyone on the account, their role, and when they were last in the dashboard. It requires the Team roles capability.
Inviting someone
Invite teammate: enter their email address and choose a role. They are emailed a one-time sign-in link. Nothing on the account changes until they use it, so an invitation sent to a typo does nothing at all.
There are no passwords anywhere in this product. Everyone signs in with a link sent to their address, which means there is no shared credential to leak and nothing to rotate when somebody leaves; removing them is enough.
The four roles
| Role | Can do |
|---|---|
| Owner | Everything, including billing, API keys, creating and deleting status pages, and deleting the account. |
| Admin | Everything except deleting the account or granting ownership. |
| Member | Monitors, incidents, maintenance and branding. No billing, API keys, subscriber addresses, subscriber export or team changes. Existing monitor request settings are private; names, groups, intervals and automatic incidents remain editable. |
| Viewer | Read operational dashboard information and change nothing. Stored monitor credentials, private request settings and subscriber details are excluded. |
Member is the right default for most people. It covers everything needed during an incident and nothing that costs money or hands out access.
Only an owner can make someone else an owner. An account can have more than one, and having a second is worth arranging before you need it; a single owner on holiday is an account nobody can change.
Confirming it is you
A few actions ask for a second confirmation even from an owner: saving or deleting a chat destination, and exporting the subscriber list. The console emails you a link; click it and the action goes through. It is the same sign-in mechanism, used once more for the actions that hand your customers' addresses to a third place.
Removing someone
Removal is immediate: their session stops working and their sign-in links stop resolving. The monitors and incidents they created are unaffected.
An API key belongs to the status page rather than to the person who generated it, so removing somebody does not revoke the keys they made. Revoke those separately in Settings → API keys if that is what you intend.
The Last seen column is the fastest way to find accounts nobody has used in a year.
API keys
Settings → API keys is where owners and admins create the credentials the developer APIs use. Each key has a name and a scope, is shown once when created, and can be revoked at any time. What each key did is in the audit log.