Seats: who can join an organisation

Limits by plan

Free and Indie each include one seat. These are plans for a single person, and the limit is stated plainly rather than dressed up as something broader. Team includes unlimited seats at no per-seat charge: invite the whole engineering team, an agency collaborator, whoever needs to see the alerts they will be paged for.

Unlimited does not mean unmanaged. Members join by invitation and leave when removed, and removing a member revokes their access immediately even though it frees no number, because on Team there is no number to free. On the single-seat plans the ceiling is enforced by the same entitlement machinery as every other limit, so an invitation beyond it is refused with a plain message rather than failing silently.

Changing size

Seats exist to price people, not readers: alert delivery reaches inboxes and channels regardless of membership, so widening visibility rarely requires widening headcount. An organisation of five who all watch a shared Discord channel fits comfortably inside a single-seat plan, while a two-person team that both sign in needs the second seat on the day it hires.

Moving from Indie to Team lifts the seat ceiling the moment the subscription is active, since entitlements are recomputed from the plan and status rather than cached. Moving back down to a single-seat plan expects the organisation to be down to one member; the interface walks you through trimming invitations first so nobody is surprised by a lockout.

Related questions

Do collaborators viewing a shared Slack channel consume seats?

No. People reading alerts in Slack, Discord or email are not members of your organisation and use no seat. Seats count people who sign in to RowShield itself.