Share

Team and organisations

Everything you create belongs to an organisation. You start with a personal one; you can create more (agencies keep one per client) and invite people into each with a role. Your plan sets how many members an organisation may have.

Organisations

The switcher at the top of the sidebar lists every organisation you belong to with your role in it. New organisation creates one owned by you. The organisation has its own monitors, servers, channels, status pages, incidents, API tokens, webhooks, integrations, reports, billing and settings. Platform administrators (the people who run the installation) can open any organisation.

Roles

Built-in roles and what they may do:

PermissionOwnerAdministratorManagerDeveloperViewer
View monitorsyesyesyesyesyes
Add and edit monitorsyesyesyesyes–
View serversyesyesyesyesyes
Add and edit serversyesyesyes––
View incidentsyesyesyesyesyes
Manage incidentsyesyesyesyes–
Manage alert channels (and maintenance)yesyesyes––
Manage status pagesyesyesyes––
View reportsyesyesyesyesyes
Manage team membersyesyes–––
Manage billingyes––––
Manage API tokens and webhooksyesyes–yes–
Organisation settingsyesyes–––

The owner is the user who created the organisation (or inherited it). When an owner deletes their account, the organisation is handed to its first administrator, else its first member; an organisation with nobody else is deleted with everything in it.

Custom roles

Team → Roles → New role: a code, a name and a set of the permissions above. Custom roles are per organisation and can be assigned to members like the built-in ones.

Invitations

Team → Invite member: e-mail address and role. The invitee receives an e-mail ("<name> invited you to <org> as <role>") with a link /invite/<token>. Someone who already has an account is added on acceptance; someone new creates an account first. Pending invitations are listed with the option to resend or cancel; members can have their role changed or be removed (their own monitors stay with the organisation).

API tokens and the team

An API token is created by a member and acts as that member inside the organisation: it can never do more than the member's role allows, whatever scopes it has. Tokens are listed under API & webhooks with their creator; revoking is immediate.

Was this page helpful?

One click helps us improve these docs.

Share this pagePlain links - no trackers, nothing loaded until you click.