Browse the docs

Team members and roles

Invite people, choose organisation or workspace roles, and see exactly what each role can do.

On this page
  1. Invite someone
  2. Organisation roles
  3. Workspace roles
  4. Permissions behind the roles
  5. Change or remove
  6. Limits
  7. API

Members are people with access to your organisation or to one of its workspaces. Each has a role, and a role is a fixed set of permissions. The dashboard hides what a member cannot do; the API enforces it.

Invite someone

The Members settings with the member list and roles
Settings, Members: everyone with access, their scope and role.
  1. Settings, Members, then Invite

    Enter their email address.

  2. Choose the scope

    Organisation-wide, or one workspace. This decides which roles are offered.

  3. Choose the role

    See the tables below.

  4. Send

    If they already have a Status Bee account, they are added immediately and see the workspace at their next sign-in. Otherwise they get an email with a link that creates their account, already confirmed, and lands them in your workspace. If the email cannot be delivered, the dashboard shows the invite link so you can send it yourself.

Pending invitations can be re-sent from the list. Inviting your own address is refused.

Organisation roles

Apply to every workspace in the organisation, now and in future.

RoleCan
OwnerEverything, including billing, API keys, members and organisation settings. An organisation always keeps at least one owner.
AdminEverything an owner can except billing.
BillingSee and manage the subscription. Read-only elsewhere.

Workspace roles

Apply to one workspace only. A person can hold roles in several workspaces.

RoleCan
Workspace adminEverything inside the workspace, including inviting workspace members.
Incident managerReport and update incidents, schedule maintenance, manage templates, read subscribers and analytics.
Maintenance managerSchedule and run maintenance windows. Read-only elsewhere.
EditorManage pages, components, monitors and templates. Cannot publish incidents.
ViewerRead everything. Change nothing.

Permissions behind the roles

For the exact mapping, these are the permissions each role holds. Useful when reading the audit log or the API reference, which name permissions rather than roles.

PermissionOwnerAdminBillingWS adminIncident mgrMaint. mgrEditorViewer
org.manage
billing.manage
members.manage
api_keys.manage
workspace.settings
pages.manage, components.manage
incidents.manage
maintenance.manage
templates.manage
monitors.manage
subscribers.read
subscribers.manage, webhooks.manage, audit.read
analytics.read
dashboard.read

Change or remove

From the member's row: change the role (within the same scope) or remove them. Removing revokes access at their next request. The last owner cannot be demoted or removed.

Limits

Plans set the number of members per organisation: 1 on Free, 5 on Starter, 15 on Team. Pending invitations count.

API

Members are managed under /user/orgs/:orgId/members. See Organizations and members in the API reference.