Seats & Billing
The number of people your team can have is a seat limit that comes from the owner's subscription plan. This page explains how the limit is calculated, when it is enforced, and how to raise it.
Seats come from the owner's plan
A team's seat limit is the owner's plan value max_team_members. Billing is always the owner's responsibility β only the owner holds the manage_billing capability (see Roles & Permissions), and only the owner's subscription determines how many seats the team has.
Each plan tier includes a different number of seats. Higher tiers include more; Enterprise plans can have custom limits set per account.
What counts toward the limit
When checking whether there is room for one more person, StatusRadar counts:
used = active team members + pending (unexpired) invitationsA seat is occupied the moment you invite someone β pending invitations reserve seats so two admins can't both invite the last seat. The seat is released if the invitation is declined or expires (default 7 days).
| Counts as a used seat | Does not count |
|---|---|
| The owner | Declined invitations |
| Every active member (admin, member, viewer) | Expired invitations |
| Every pending, unexpired invitation | Members who left or were removed |
The owner always occupies one seat, so a plan with max_team_members = 1 is effectively a solo (personal) team with no room to invite others.
When the limit is enforced
The seat cap is checked at two points, so it cannot be bypassed by a race between sending and accepting:
- At invite time β If
used >= max, the invite is rejected: "Your plan allows N team member(s). Upgrade your plan to invite more." - At accept time β Re-checked inside the membership transaction. If the team filled up in the meantime, acceptance fails: "This team has reached its member limit. Ask the owner to upgrade the plan."
Default limits
Plans set max_team_members individually. When no active subscription exists, the account falls back to the default plan; the built-in floor is a single seat:
Seats (max_team_members) |
|
|---|---|
| Default / free fallback | 1 |
| Paid plans | Higher, per plan tier |
| Enterprise | Custom |
Custom per-account overrides (custom_max_team_members) take precedence over the plan value when set, so an Enterprise or specially provisioned account can have a tailored seat count.
Raising your seat limit
To add more seats:
- As the owner, go to Dashboard β Billing.
- Upgrade to a plan with a higher
max_team_members. - The new limit applies immediately β invite the additional members from Dashboard β Settings β Team.
If you only need short-term capacity, remember that removing inactive members or letting unused pending invitations expire frees their seats.
Frequently asked
Does each member need their own subscription? No. The team shares the owner's plan. Members do not pay separately; they consume the owner's seats and quotas.
Who pays when I'm invited to a team? The team owner. Your own personal team and any personal subscription are unaffected by joining someone else's team.
What happens to seats when a member leaves or is removed? The seat is freed immediately and the person is moved back to their own personal team.
Do other plan quotas apply per team too? Yes. Monitors, status pages, servers, alert channels, data retention, probe locations, and observability quotas are all governed by the owner's plan. See Seats & Billing for seats; quotas are documented under their respective sections.
Next Steps
- Invitations - Inviting members and the accept flow
- Roles & Permissions - Who can manage billing and members
- Teams Overview - Company sub-accounts concept
- Quotas - Observability usage limits and top-ups