Quick answer
Codex on a Business plan gives each seat its own short and weekly windows rather than one shared pool. Admins get organization-level billing and seat management, but not per-project token detail. Confirm the seat allowance and whether credits can be pooled before you standardise on it.
How the allowance is structured
| Item | Per seat | Organization |
|---|---|---|
| Short window | Own allowance | Not shared |
| Weekly window | Own allowance | Not shared |
| Credits | Optional top-up | May be pooled by policy |
| Reporting | Usage panel | Admin console |
| Data controls | Account settings | Org policy |
Before a rollout
- Confirm the current per-seat allowance in the admin console.
- Check whether credits are pooled or individual.
- Decide who can enable API billing for overflow.
- Agree whether local session data may be exported for reporting.
- Pilot with five developers for two weeks before buying more seats.
What to watch after rollout
- Seats that never hit a window: candidates for reclamation.
- Seats that hit the weekly window every week: candidates for overflow policy.
- Projects with unusually high tokens per change.
- Developers running several agents in parallel without a budget.
What changes on a business plan
Business plans change administration more than metering. Seats are managed centrally, usage may be pooled or capped, and data handling terms differ from a personal account. The individual windows usually still apply, which surprises teams that expect one shared allowance.
| Area | Personal | Business |
|---|---|---|
| Billing | Card | Invoice or contract |
| Seats | One | Admin-managed |
| Usage | Your windows | Windows plus admin caps |
| Data terms | Consumer terms | Contract terms |
Ask two questions before rolling out: whether seats share capacity, and whether admins can see usage. The answers decide your team reporting design.
Questions, answered
Do Business seats share one Codex allowance?
No. Each seat has its own windows. Sharing a login is not a workaround and breaks attribution.
Can admins see per-developer token usage?
Admins see seat and billing reporting. Per-project token detail stays in local session files unless you collect aggregates.
Are credits pooled on Business?
That depends on the organization's settings. Check the admin console before assuming either way.
