Skip to content

Users, roles and organisations

Invite your team, decide what each person may do, and see how alerts reach the members of an organisation.

An organisation is the place your monitors, incidents, status pages and on-call rules live in. The people who work in it are its users: each has their own login and a role that says what they may do there.

The four roles

WhatViewerMemberAdminOwner
See monitors, incidents, status pages, messages and on-call✓✓✓✓
Be alerted; acknowledge an incident (app or SMS ACK)✓✓✓✓
Create, edit, pause, test and delete monitors✓✓✓
Snooze and resolve incidents, add notes; post status page updates and maintenance✓✓✓
Status pages, rotations, escalation policies, integrations, private locations✓✓
Invite and remove users, change roles, organisation settings, API tokens✓✓
Plan, billing and invoices; transfer ownership✓

Whatever the role, everybody changes only their own profile: name, password, two-step sign-in and phone number. Where your role does not allow something, the app shows the control disabled and says which role it needs.

Inviting people

An admin or the owner opens Settings → Users → Invite, enters an e-mail address and picks a role. The person gets an e-mail with a link that is valid for 7 days and works only for that address. Somebody new to Heimdall chooses a name and a password on the page behind the link; somebody who already has a login signs in and accepts. An open invitation counts as one of the plan’s users (Free: 2, Pro: 5, Team: unlimited, Business: unlimited). Invitations can be sent again or revoked.

Alerts go to members

  • The people Heimdall alerts are the organisation’s users. There is no separate list of contacts to maintain.
  • Each user adds their own phone number in Profile → Notifications and confirms it on that phone. Nobody can add or change a number for somebody else; admins see only whether a number is confirmed, with the number masked.
  • The “is alerted” switch (Settings → Users, or On-call → People) says whether the default rule alerts a member in this organisation. Switch it off for somebody who has a login but need not be woken. An escalation policy step that names a person reaches them anyway.
  • One number, one Telegram chat and one set of quiet hours per login: they apply in every organisation that login works in.

Leaving and removing

An admin removes a user under Settings → Users; anybody but the owner can leave an organisation there. Either way access ends at once, the person is told by e-mail, and their login stays theirs. If a rotation or an escalation policy still names the person, Heimdall asks to change that first, so that no alert is left pointing at nobody. Somebody who is no longer a member of any organisation can start one of their own or delete their login.

Transferring ownership

An organisation has exactly one owner. The owner hands it over under Settings → Users → Transfer ownership, to an admin or a member, confirming with their password (and a code, with two-step sign-in). The new owner manages the plan and billing from then on; the previous owner becomes an admin. Both are told by e-mail.

Requiring two-step sign-in

Under Settings → Organisation an admin can require two-step sign-in for every member. Members who have not set it up can still sign in, but everything in that organisation except their own profile stays closed until they have.

Working in several organisations

One login can be a member of several organisations — your own and a customer’s, for example — with a different role in each. The account menu lists them and switches between them. Your phone number, Telegram and quiet hours come with you; monitors, incidents, status pages, on-call rules and API tokens belong to each organisation separately.

Several organisations in one account

An account is its first organisation: the one you created when you signed up. Its plan says how many organisations the account may have (Free: 1, Pro: 1, Team: 2, Business: 5). Use a second one to keep a product, a team or a customer apart, with its own members.

Shared by the accountSeparate in each organisation
The plan, the trial, the subscription, invoices and add-onsMonitors, their history and incidents
Every limit of the plan: running monitors, status pages, private locations, usersStatus pages and their subscribers
The monthly SMS and call quota (fair use)On-call: who is alerted, rotations, escalation policies, integrations
The owner: one person owns every organisation of the accountMembers and their roles, invitations, API tokens, settings
  • Only the owner adds an organisation: account menu → New organisation. The owner is its owner too, and invites its members there. Somebody who works in two organisations of one account is counted as one user.
  • Usage on the billing page shows the account’s numbers against the plan and, under each, how much of it is the organisation you are working in.
  • Only the owner deletes an organisation, under Settings → Organisation, with their password (and a code, with two-step sign-in). Its monitors stop and its status pages go offline at once; its members keep their logins and are told by e-mail. Everything in it is erased 30 days later — until then, write to support to bring it back. Its place is free again right away.
  • The first organisation cannot be deleted by itself: it goes only with the account (Profile → Privacy & data → delete account), which closes every organisation of the account.