Documentation

Team

Who may do what: the five roles, how invitations and limits work, what the audit log records, how API tokens are limited and how you secure your account.

On this page

Roles

Every member has exactly one role per organization. The permissions build on each other:

  • Owner: everything, including billing, deleting the organization and granting the owner role. The last owner cannot be removed or demoted.
  • Admin: like owner without billing and deleting the organization. Manages members, channels, rules, integrations, API tokens, chat commands, calendar subscription, branding, audit log and data export.
  • Member: create and edit clients, domains, monitors, maintenance windows, status pages and report links, trigger checks, create records in one click, acknowledge incidents. Sees channels, members and usage but does not change them.
  • Viewer: the whole inside view of the organization without changing anything. Receives no alert mails to the members.
  • Client: read-only and only the domains of one client, described in the Clients chapter.
  • Rank: owner above admin above member above viewer and client. You only change or remove members of equal or lower rank; owners only by owners.

See also: Client access

Invitations and limits

Owners and admins invite by email under Settings → Members, with the role admin, member, viewer or client; the owner role is only granted by a role change. An invitation is valid for seven days, bound to the address, replaces an older open invitation to the same address and can be withdrawn. The invitee signs up with this address or signs in with it and accepts.

The member limit of the plan counts team members and open team invitations: 2 on Free, 5 on Freelancer, 15 on Agency, 50 on Agency Pro. Client access does not count. Whoever loses the organization immediately loses their API tokens as well.

Audit log

Under Settings → Log, owners and admins see who did what and when: sign-ins and failed sign-ins, password, two-factor and passkey changes, invitations, joins, role changes and removals, clients created and deleted, status pages enabled and disabled, domains created and deleted, maintenance windows, channels and rules, API tokens created and revoked, integrations, one-click records, calendar addresses, chat commands, branding, billing and data export. Every entry carries action, user, object, changed fields, IP address and browser; entries are immutable and deleted after 24 months. According to the plan, the audit log is included from Agency upwards.

API tokens

Owners and admins create tokens for the REST API under Settings → API. A token belongs to exactly one organization, has the scope read (like viewer) or write (like member), never admin or owner rights, and an optional expiry of 1 to 730 days. It is shown in plain text exactly once; afterwards name, scope, last use and expiry are visible. At most 20 active tokens per organization, 300 requests per minute and token.

Not reachable with a token: account, password, two-factor, passkeys, members, invitations, billing, channels, audit log, data export and token management itself.

See also: API documentation

Two-factor and passkeys

Under Settings → Security every user sets up TOTP with recovery codes or passkeys (WebAuthn) for their account; a passkey signs in without a password and counts as a second factor. This applies to all roles including client access. A password change signs out other sessions.

Data export and deletion

Owners and admins export all data as JSON under Settings → Organization: organization, members, channels without secrets, clients and domains with notes and monitors, maintenance windows as well as incidents, events and audit log of the last 90 days; five times per hour. Owners can delete the organization. Agencies monitoring client domains receive a data processing agreement on request.

See also: Privacy policy

Frequently asked questions

Can a member belong to several organizations?
Yes, with their own role per organization; the dashboard switches between them. API tokens, however, are per organization.
Who receives the alert mails?
Owners, admins and members, unless they switched alerts off in their profile, each with their personal minimum severity. Viewer roles and client access do not. Additionally up to 20 fixed addresses per email channel.
What happens to the tokens of a removed member?
They become invalid immediately; calls respond with 401. The action is recorded in the audit log.