​

Seats & membership capacity

Seats represent the number of organization members covered by a seat-based plan when that billing model is enabled.

​

Seats are a billing concept

A member can require an organization seat even when they do not have an administrator role. Seat usage and role permission are separate concerns.

​

Before inviting

Check:

• current seat count
• active/pending membership
• plan rules
• whether adding a seat changes subscription billing
• whether the member actually needs organization access

​

Pending invitations

Whether a pending invitation reserves a seat depends on the active billing implementation. The organization-management surface should be treated as the source of truth for current seat consumption.

​

Add or remove seats

When seat changes are supported, Starfire should update the organization subscription relationship and resulting entitlements without creating a disconnected duplicate subscription.

​

Removing members

Removing a member can reduce active seat usage according to the current billing rules. It does not automatically cancel the organization subscription or delete resources the organization owns.

​

Downgrades

Before reducing seat capacity below current membership, resolve which members should remain active. Starfire should not silently delete organization members merely to satisfy a lower seat count.

​

Troubleshooting

If invitation capacity and billed seat count disagree, inspect:

• organization membership
• pending invitation policy
• BillingAccount
• Stripe subscription item/quantity when applicable
• reconciliation state