Getting started
Workspaces, teams, and roles
Understand Billing Owner, Account Admin, Team Manager, and Member permissions, ownership transfer, and team-scoped access in MonoDuty.
Workspace model
A MonoDuty account is a workspace. A workspace contains teams; teams own services, alert sources, on-call schedules, and escalation policies. A person can belong to several teams, but each team has exactly one Team Manager.
Every workspace has exactly one Billing Owner. This invariant prevents an account from becoming ownerless and gives billing, legal ownership, and account deletion a single accountable owner.
Roles
| Role | Scope | Purpose |
|---|---|---|
| Billing Owner | Whole workspace | Owns the subscription, billing changes, ownership transfer, and account deletion. |
| Account Admin | Whole workspace | Manages users, teams, operational settings, invoices, sources, schedules, and policies. Pro allows up to 3; Business allows up to 10. |
| Team Manager | One team | Manages members, sources, schedules, overrides, and escalation policies for their own team only. |
| Member | Assigned teams | Receives alerts, views their team incidents, manages their own profile and overrides, and can acknowledge or resolve incidents. |
Permission boundaries
Billing Owner and Account Admin can invite or remove users, create or delete teams, assign Team Managers, export incidents, and view account-wide usage. Only the Billing Owner can request a sales-assisted plan change, transfer ownership, or delete the account; self-service checkout is not currently available.
Team Manager access is always checked against the team that owns the resource. Being a Team Manager in one team never grants access to another team's sources, schedules, policies, or incident history. Members can acknowledge and resolve incidents but cannot change account or team configuration.
Ownership and offboarding
Ownership transfer is atomic: the recipient must be an active, verified workspace member, and the workspace always retains one Billing Owner. Removing a user immediately revokes workspace access, team memberships, current overrides, direct assignments, and pending notifications while preserving historical incident and audit records.
Pending invitations reserve a seat until accepted, cancelled, or expired. This keeps concurrent invitations from exceeding a plan's seat allowance.