Company, teams and seats
A Roadmap Flow Team plan is bought by a company, not by a team. The company owns the subscription and one pool of licensed seats, and it can contain as many teams as you like. Understanding that takes a minute and answers the two questions every administrator eventually asks: how many seats does one person in four teams use, and why did archiving a team not remove anybody?
The shape of it
Company one subscription, one pool of licensed seats
├── company members seats are counted HERE
└── teams grouping only
└── team members never a seat- The company owns the Stripe subscription and the seat pool.
- Company membership is what makes someone part of the company. It carries a company role, a state (active, suspended, removed) and either a licensed seat or no seat.
- Teams group people inside the company. A team has no subscription, no seat pool and no billing of its own.
The one rule that surprises everyone
A seat is one unique active company member holding a licensed seat.
Not team memberships. Not devices. Not invitations. Not sign-ins. One person in ten teams costs one seat.
This is calculated in exactly one place in the product, so the number on the Overview page, the number on the Seats and billing page and the number Stripe bills you for cannot drift apart.
The four numbers on the seats bar
- Purchased — the quantity on your Stripe subscription. This is what you pay for.
- Assigned — active company members holding a licensed seat. This is what you are using.
- Reserved — pending invitations that are holding a seat. Zero unless your company uses the strict seat policy; see Company settings.
- Available — purchased minus assigned minus reserved, never below zero.
What uses a seat
- A member — the ordinary role. Licensed by default.
- A company admin — licensed by default.
- A billing admin — licensed by default, though the licence buys them nothing they can use, because their role does not grant access to roadmap content. If your finance contact never opens Roadmap Flow, take their seat away and you get it back.
- The company owner — always licensed. The owner cannot be unlicensed while they are the owner.
What does not use a seat
- A viewer. Viewers are unlicensed by default, which means you can add read-only people beyond your purchased seat count.
- Team membership, however many teams.
- A suspended or removed person. Suspending someone releases their seat immediately.
- A pending invitation, under the default seat policy.
- An archived team. Archiving hides a team. It removes nobody's account, nobody's company membership and nobody's seat.
Where the numbers come from
Purchased seats are the Stripe subscription quantity, so the only way to change them is a real subscription change — done from Seats and billing, which sends it to Stripe. Assigned seats are a count of your own people, so they change the moment you invite, suspend, unlicense or remove somebody. Nothing you do on the People page changes what you pay until you also change the quantity.