Inviting your team
Add teammates to your organization and give them a role.
An organization can hold multiple members, each with a role that decides what they can see and change. The short version below is enough to send an invite; the full per-action matrix lives in Roles & permissions.
Roles at a glance
- Owner — full access, including billing, deleting the organization, and transferring ownership. Exactly one per organization.
- Admin — manage monitors, status pages, incidents, integrations, members and billing. Cannot delete the organization.
- Billing — manage the subscription, payment method and invoices. Read-only for everything else.
- Member — manage monitors, status pages, incidents and integrations. Cannot manage members or billing.
- Viewer — read-only access to the dashboard.
Sending an invite
- Go to Organization → Members.
- Click Invite Member.
- Enter the email address and pick a role.
- Click Send Invite. The invitee gets an email with an accept link.
Free includes 2 members, Starter 8, Growth 25, and Scale is unlimited. The current count against the limit sits at the top of the Members page. Pending invites hold a seat until they are accepted or revoked; removing a member or revoking an invite frees the seat immediately.
Managing members
From the Members page you can change a member's role or remove them. A removed member loses dashboard access immediately. Anything they created — monitors, status pages, integrations — stays exactly where it is.
The Owner's own role cannot be changed from this page. To hand the organization to someone else, see Transferring ownership.
Multiple organizations
One user account can belong to several organizations, with a different role in each. Switch between them with the picker at the top of the sidebar. Data is scoped per organization: every read and write is checked against your membership in the organization that owns the record.
What is not available
There is no API for inviting members or changing roles — these are dashboard-only. There is no SSO or SAML sign-in; sign-in is email and password with session cookies. SSO is on the roadmap and has never shipped, despite an earlier version of this site listing it.