Team and workspaces
Everything you create belongs to an organisation. People join it with a role, and can be confined to part of it.
Roles
| Role | Can |
|---|---|
| Owner | Everything, including billing, deleting the organisation, and removing other owners. |
| Admin | Everything except billing and deleting the organisation. Can invite and remove people. |
| Editor | Create and change monitors, channels, status pages and maintenance. Cannot manage people or billing. |
| Responder | Acknowledge and resolve incidents and run maintenance. Changes no configuration. |
| Viewer | Read-only. The right role for a client user. |
| Billing | Invoices and payment method only. Sees no monitoring data. |
An organisation always has at least one owner; the last one cannot be removed or demoted.
Inviting somebody
Invite by email address and they get a link. If they already have an account with that address, accepting adds the organisation to it — they do not need a second account, and they can switch between organisations from the sidebar.
The invitation only works for the address it was sent to. A forwarded link is refused rather than letting whoever received it join, because invitations get forwarded constantly and usually innocently.
Workspaces
A workspace is a folder for monitors, status pages and channels. Every organisation has one by default and most never need a second.
They matter for agencies, on Pro and above: a member confined to a workspace sees only what is in it. Not a filtered view — the rest does not exist for them, in the dashboard and in the API alike. A contractor working on one client sees that client and nothing else, and a status page can only publish monitors from its own workspace, so one client’s monitor cannot appear on another’s page.
When somebody leaves
Removing a member revokes their membership and their API keys immediately, anddeletes their personal alert channels — their handset, their private Telegram chat, their mobile number.
That last part is worth knowing before you build an escalation policy around a colleague’s phone. Shared channels are untouched: a #alerts webhook or a distribution list belongs to the organisation and survives any departure. See Alerts and channels for which is which.
Single sign-on
On Enterprise, which is arranged by talking to us rather than bought from the pricing page. Register your identity provider in Settings → SSO, prove you control the email domain by publishing a DNS record we give you, and people at that domain sign in through your provider.
The DNS check is not a formality. SSO routes on an email domain, so without proving the domain is yours, a provider claiming a public domain could capture every account on it. A provider that has not passed the check never participates in sign-in.
API keys
A key is issued against one membership and inherits that person’s role and workspace confinement — a key made by a member confined to one workspace can reach only that workspace. Keys are shown once, at creation.
Rate limits are per organisation rather than per key, because another key is free to mint and a per-key ceiling would bound nothing.
Audit log
Every change to configuration is recorded with who made it and what changed — monitors, channels, status pages, members, roles, keys.
Entries are recorded on every plan; Business and above can read them. That way upgrading opens the whole history rather than starting one from the day you upgraded.
Credentials, hashes and secrets are never written into it.