Quick answer
On individual plans, one person owns the session and weekly windows. On Team and Enterprise, each seat has its own allowance with organization controls. Admins see seat and billing reporting; per-project tokens stay in each developer's local Claude Code logs unless the team collects aggregates.
How the allowance is structured
| Plan | Window owner | Admin visibility |
|---|---|---|
| Individual | The account | None |
| Team | Per seat | Seat and usage report |
| Enterprise | Per seat, contract | More reporting and policy |
| API | Per key | Usage dashboard |
Measure without surveillance
- Agree which fields matter: tokens, model, project, date.
- Have each developer run a local tracker.
- Export aggregates, not transcripts.
- Report by team and project before person.
- Delete raw exports on a schedule.
Interpret the numbers
- A blocked seat is a capacity problem, not a performance signal.
- High usage can mean high output or a retry loop.
- Compare the same task type across seats.
- Use the data to size plans, not to rank people.
Size seats with data
Per-developer limits matter because Claude plans are per seat and the windows are per account. One developer running agents all day will exhaust a seat that suits another developer perfectly, and no amount of policy fixes that mismatch.
| Role | Typical pattern | Seat sizing |
|---|---|---|
| Occasional reviewer | Chat plus small edits | Entry tier |
| Feature developer | Daily sessions | Mid tier |
| Agent-heavy work | Parallel long runs | Top tier |
| Platform and tooling | Spiky, project-based | Mid tier plus API fallback |
Measure a month before committing: estimated spend and team usage.
Questions, answered
Do Team seats share one Claude limit?
Each seat has its own allowance. Organization policy controls access and billing.
Can an admin see each developer's tokens?
Usually at the seat level. Per-project token detail is local unless you collect aggregates.
Does Claude Code Enterprise remove limits?
No. It changes administration and capacity, not the existence of usage windows.