Teams Overview

Teams let a company share monitors, status pages, servers, alerts, and observability apps across multiple people under one account, with role-based access control and a single billing relationship.

Company sub-accounts

In StatusRadar every user belongs to a company team (sometimes called a sub-account). A team is the container that owns your resources — monitors, status pages, servers, alert channels, incidents, and observability apps all belong to a team rather than to an individual user.

• Every account has a team. When you register, a personal team is provisioned automatically and named after you (for example, Jane's Team). You are its owner.
• One active team at a time. Your session always operates "inside" one team — your active team. Reads and writes apply to that team's resources only.
• Exactly one owner per team. The owner holds billing and is the only role that can transfer ownership or delete the company. This invariant is enforced at the data layer and never drifts.
• Members keep their own personal team. If you are removed from (or leave) a team, your active team automatically switches back to your own personal team so you are never locked out.

How resources are shared

Once you are a member of a team, you see and work with that team's shared resources according to your role:

What you can do with these resources depends on your role. Any member can view them; mutations require the matching capability. See Roles & Permissions.

Membership lifecycle

1. An owner or admin invites someone by email and assigns a role (admin, member, or viewer).
2. The invitee receives an email with a secure link and accepts while logged in as the invited address.
3. On acceptance, the user joins the team and their active team switches to it.
4. Owners and admins can change roles or remove members at any time.
5. Any non-owner member can leave the team; the owner must transfer ownership first.

Full details: Invitations.

Managing your team

Team management lives in the unified settings hub:

Dashboard → Settings → Team (/dashboard/settings?tab=team)

From there, owners and admins can invite members, change roles, remove members, and (owner only) transfer ownership. The member list shows each person's name, email, role, and join date, ordered owner → admin → member → viewer.

Seats and billing

The number of people you can have in a team is a seat limit tied to the owner's subscription plan (max_team_members). Active members plus pending invitations count against that limit, and the cap is enforced both when sending an invite and again when the invite is accepted.

See Seats & Billing for how the limit is calculated and how to raise it.

Next Steps

• Roles & Permissions - The owner/admin/member/viewer capability matrix
• Invitations - Inviting members by email and the accept flow
• Seats & Billing - How seat limits and plans work
• Monitors Overview - The resources your team shares