Teams and seats
A team shares one subscription. One person buys, creates a team, and their members inherit the plan up to the seat count that was paid for.
Seats come from the price list
Section titled “Seats come from the price list”Nothing anywhere says “teams are a Utility feature”. The seat arithmetic says it:
| Plan | Seats, including the subscriber |
|---|---|
| Free | 1 |
| Pro | 1 - sold per named user, so a Pro subscription covers only the subscriber and cannot add anyone |
| Utility | 10 - sold per 10 users, so it can |
To bring colleagues on, move to a plan with seats to give.
Inviting people
Section titled “Inviting people”Invite by email address, and give each member a role:
- Owner - created the team, holds the subscription
- Admin - can invite and remove members
- Member - inherits the plan
What the team shares, and what it does not
Section titled “What the team shares, and what it does not”The team distributes entitlement. It does not own the billing: the subscription stays with the person who bought it, and their invoices and payment method are unchanged.
Seat limits are enforced server-side, so adding a member beyond the seats you hold is refused by the server with a prompt to upgrade rather than being allowed and reconciled later.
Projects are shared separately, per project - see sharing. Joining a team does not by itself give anyone your models.