Roles and permissions

Unit Oncall has two independent layers of roles:

Organization roles control who can manage the Organization itself — its members, settings, billing, and deletion.
Team roles control who can manage a specific Team — its schedule, its members, and its integrations.

A person has exactly one Organization role and a (possibly different) role in each Team they belong to. The layers are separate: being an Organization admin does not by itself make you a team_admin of every Team, and a plain Organization member can still be the team_admin of a Team they run.

Organization roles

Role	Intended for	Summary
`owner`	The person who owns the Organization.	Full control, including deletion and ownership transfer.
`admin`	Day-to-day administrators.	Manage members and settings.
`billing`	Finance / procurement.	Billing only — how much of it is decided by the Organization's billing scope.
`member`	Everyone else.	Use the product; no Organization-level administration.

What each Organization role can do

Action	owner	admin	billing	member
Manage members (invite, remove, change roles)	✓	✓	—	—
Manage Organization settings	✓	✓	—	—
View and manage billing (see below)	✓	Configurable	Configurable	—
Change the plan, cancel or resume the subscription	✓	—	—	—
View audit logs (Business plan and above)	✓	—	—	—
Delete the Organization / transfer ownership	✓	—	—	—
Belong to Teams and respond to incidents	✓	✓	—	✓

The owner, admin, and member roles can be added to Teams and take part in on-call work. What they can do inside a Team is then governed by their Team role, not their Organization role. The billing role is intentionally finance-only and cannot be added to Teams — its purpose is to give finance or procurement staff access to billing without giving them on-call responsibilities.

Who can manage billing

Unlike the other rows in the table above, View and manage billing is not fixed — each Organization decides how wide it is with the billing scope setting. A person holds exactly one Organization role, so without this setting an Organization whose administrators also handle finance would have no way to express that.

Billing scope	owner	admin	billing	member
`owner`	✓	—	—	—
`owner_and_billing` (default)	✓	—	✓	—
`owner_billing_admin`	✓	✓	✓	—

A new Organization starts on owner_and_billing. Choose owner to keep finance with the owner alone, or owner_billing_admin if your administrators handle finance too and you would rather not use the billing role at all.

The scope covers viewing billing data (subscription, usage, credits, invoices) and the billing operations — starting a subscription, updating the payment method, buying credit top-ups, and setting the credit consumption order. It is edited on the Billing view of the Organization, together with the other billing settings, and only the roles it currently allows can change it. It is deliberately not part of the Organization settings document, so that an administrator cannot widen their own finance access.

Three operations stay with the owner whatever the scope is: changing the plan, cancelling the subscription, and resuming a cancelled one. These change or end an existing contract, so they sit with the person who owns it — next to deleting the Organization. Starting the first subscription follows the scope instead, so whichever role the scope allows can put the Organization on a paid plan. See Plans and billing.

Team roles

Role	What it can do
`team_admin`	Manage the Team: edit the schedule, manage Team members, and configure the Team's webhook and rules.
`team_member`	Take part in the Team's schedule and respond to alerts.

See Team configuration for how Teams and their members are defined.

Assigning roles

The Organization role is chosen when a member is invited and can be changed later by an owner or admin.
The Team role is chosen when a person is added to a Team.

Only owners and admins can manage Organization members and change Organization roles. Only the owner can delete the Organization or transfer ownership to someone else.

Authentication — how members sign in before any role applies.
Audit logs — role changes and member management are recorded.
Team configuration — Team-level membership and roles.
Organization settings — Organization-wide governance options.