Skip to main content
Team members share one credit pool. This page covers who can manage whom, how seats are counted, and what is really happening behind each error.

​
Three roles

Owner and Admin have identical portal permissions. The gate only asks “is this an active owner or admin,” and both pass the same check. The only difference is three Owner protections: the Owner cannot be removed, demoted, or suspended.Transferring ownership currently requires contacting support.
Member status is one of three values: active, invited (sent but not accepted), or suspended.

​
Invitations

An invitation is fundamentally a link carrying a token. The email field is optional: supply one and the system sends the mail, omit it and you copy the link yourself.
1

Create the invite

Team portal → Members → Invite, choose a role, optionally enter an email.
2

Share the link

Copy it, or let the system email it.
3

They accept

They sign in (registering first if needed) and confirm — only then is a seat actually taken.
Invites expire after 7 days, after which the link stops working and the invite is marked expired; you send a new one.
There is no cap on pending invitations — but a seat pre-check runs at invite creation, so pending invites cannot overshoot remaining seats by much. Batch import handles at most 500 people per call.

​
How seats are counted

Only active members occupy a seat. An invitation that has been sent but not accepted does not. Seat checks run at two moments:
  1. When the invite is created (failing early beats sending invites that cannot be honored)
  2. When the person actually joins (the final verdict)
At the limit you see:
(The raw backend message is Organization has reached its seat limit.) Removing a member frees a seat immediately. The team plan defaults to 10 seats (a configurable default that operations can override — the pricing page at purchase time is authoritative). The seat cap is itself a mutable field on the organization; contact support to expand.

​
One organization per user

An account can belong to at most one organization at a time. Three layers enforce it: a database unique constraint, a service-layer pre-check, and an ownership check when opening a team. If the invitee already belongs to another team, acceptance fails:
They have to leave their current team first.

​
Failures and what to do

​
What happens when a member leaves

​
FAQ

No. Opening the link walks them through registration, after which they can join.
Yes, depending on the org’s billing mode. In shared-pool mode everyone draws from one pool; in quota mode each member has a monthly allowance, and exceeding it either blocks or passes depending on configuration. See team billing.
Yes. The portal gate distinguishes only “owner/admin” from “member,” and the first two are equivalent. Earlier versions of this page said Admins could not change settings; that was inaccurate.
Suspending keeps the membership but removes active status — no seat, no access to the team pool. Removal deletes the membership. Neither can be applied to the Owner.

​
Keep reading

Team overview

Setup flow and entitlements

Team billing

Credit pool, quota mode, and usage reports

Expiry and renewal

What freezing actually blocks

Limits

Hard limits across the platform