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 → Account → 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 member: 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.

Everyone signs in as themselves, with their own address: with a password they chose, or with a one-time link sent to that address. A password is optional. Choosing one, or a new one after forgetting it, always goes through a link sent to the address, and signs every other device out. Nothing is shared between teammates, so there is 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.
Operator	Monitors, including adding and deleting them, acknowledging outages, incidents, maintenance, branding and ordinary notification settings. No billing, API keys, team changes, on-call policies, custom domain, Slack, webhooks, email sender, subscriber addresses, subscriber export or subscriber chat destinations. 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.

Operator 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

Some actions ask for a second confirmation even from an owner:

• changing who is on the team;
• exporting the subscriber list, or saving or deleting a subscriber chat destination;
• generating or revoking an API key;
• connecting or disconnecting a custom domain;
• changing the email sender, the Slack webhook or an outbound webhook;
• changing a monitor's request settings, or rotating a heartbeat URL;
• changing the subscription;
• changing event storage or a Database Health connection;
• changing the outage page's custom code or its credentials;
• connecting the WhatsApp sender or adding a receiver;
• deleting a status page, and deleting the account.

The dashboard emails you a link; you open it and press the button again. It is the same mechanism you sign in with, used once more for actions that hand your customers' addresses to a third place, give a system access to your page, or cannot be undone. Once you open the link, the confirmation covers a single action and expires after ten minutes.

Removing someone

Removal is immediate: their session stops working, their sign-in links stop resolving and a password they set no longer signs them in. 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 Account → Access if that is what you intend.

Each row says when that person was last in the dashboard: the fastest way to find accounts nobody has used in a year.

Your account and deleting it

Account → General shows the address you are signed in with and what your role lets you do. Every role can open it. Owners and admins see Delete status page at the bottom; only an owner sees Delete account.

• Delete status page removes the selected page and what belongs to it: its monitors, incidents, subscribers, history, embeds and credentials. Your account, team, subscription and other pages stay. If the page has a custom domain or open incidents, you confirm each one first.
• Delete account removes every status page on the account with all their data, and cancels an active subscription. You type the owner's email address to confirm, and it cannot be undone. People watching your pages lose access immediately.

You can also ask for deletion by email, as the terms describe. This screen has no whole-account export. The subscriber roster downloads as CSV from Subscribers.

API keys

Account → Access 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. Generating or revoking a key asks you to confirm by email first. What each key did is in the audit log.

Next up