Docs/Teams & roles
Teams & roles
Status Harbor is multi-tenant. Every monitor, integration and Lighthouse belongs to a team. A user can belong to multiple teams and switch between them.
Roles
Three roles. The split is owner (everything), maintainer (everything except member management and team rename), member (read-only).
| Action | Owner | Maintainer | Member |
|---|---|---|---|
| View monitors, crons, incidents, status page, API tokens, Lighthouses | ✓ | ✓ | ✓ |
| Create / edit / delete monitors and crons | ✓ | ✓ | — |
| Pause / resume monitors and crons | ✓ | ✓ | — |
| Acknowledge / resolve incidents | ✓ | ✓ | — |
| Manage integrations (Slack, Telegram) | ✓ | ✓ | — |
| Edit status page settings, verify custom domain | ✓ | ✓ | — |
| Create / regenerate / revoke API tokens | ✓ | ✓ | — |
| Create / edit / delete Lighthouses, adopt discoveries | ✓ | ✓ | — |
| Edit team general settings | ✓ | ✓ | — |
| Invite, remove or change role of members | ✓ | — | — |
| Rename team | ✓ | — | — |
| Delete team | ✓ | — | — |
Roles are checked at the route layer — a Member can see everything but won't get a Create / Edit button.
Inviting
Settings → Members → Invite. Enter an email and pick a role. Status Harbor emails an invitation link; the recipient signs up (or signs in) and is dropped into the team with the role you set.
Pending invitations count against your plan's seat allowance until they're accepted or revoked.
Switching teams
Click the team picker in the dashboard header. Each team has its own monitors, integrations and billing.
Removing a member
Owner-only. Settings → Members → ⋮ → Remove. The member loses access immediately. Anything they created (monitors, tokens) stays with the team — ownership is at the team level, not the user level.
Sign-in
Google, GitHub, GitLab or email/password.