---
type: reference
title: Seats
summary: How the account's shared seat pool is consumed by troop members and troop tokens, and what is free.
---

Seats are how Caputchin counts the people and service tokens working across your troops. They are an **account-level** pool, not a per-troop count: one pool, set by your plan, covers every troop your account owns. You manage the pool size on the [billing](/docs/account-management/billing#seats) page.

## What takes a seat

| Consumes a seat | Free, never counted |
|---|---|
| A **troop member** (a person you invite) | Your [personal access token](/docs/account-management/personal-access-token) (the account's master token) |
| A **troop access token** (a service credential attached to a troop) | The troop owner is a member like any other, but no extra entity |

So the seats in use are the distinct people across all your troops, plus every troop access token attached to any of them.

## The same person counts once

A seat is tied to the person, not the membership. If you invite the same teammate into two troops, they take **one** seat, not two. This lets you spread a person across the troops they work in without paying twice.

A troop access token, by contrast, is counted per token: two tokens are two seats, even in the same troop.

## Reading your usage

The [billing](/docs/account-management/billing#seats) page shows the pool as used against total, broken down into troop members, access tokens, and how many seats remain. When the pool is full, inviting another member or attaching another token is blocked until you free a seat (remove a member or token) or raise the total in billing.

## Changing the pool size

The total is part of your subscription. Increase or decrease it on the billing page by adjusting your seat count; the [billing rules](/docs/account-management/billing#adjust-plan-and-seats) for when a change takes effect apply (increases immediately, decreases at the period end).

## See also

- [Billing](/docs/account-management/billing#seats): set the pool size and read usage.
- [Permissions and scope](/docs/troops/permissions): what a seated member can do.
- [Tokens](/docs/troops/tokens): troop tokens take a seat; the account token does not.