On a Team plan each member keeps their own included AI allowance. What the workspace adds is a shared pool of prepaid credits that covers a member's runs on the organization's projects once their own allowance is used up — so a writer with a heavy week is not stopped at the Run button while a colleague's allowance sits unused. Seats do not fill the pool: the organization's owner adds credits to it, and switches on Cover extra AI usage from the shared pool, from Settings → Organization → Shared AI credits. Team
How the pool is countedLink to this section
A run on an organization project draws the member's own allowance first — and their own credits, if they have turned on overage for themselves — and reaches the pool only for what is left. Settings → Organization shows the pool balance and each member's use this period. Runs on a member's personal projects do not touch the pool.
Per-member limitsLink to this section
The owner can set a per-period limit for each member — how much of the pool one person may use — so a single Agent Mode session cannot empty the pool for everyone. A member who reaches their limit sees it at the Run button, with the owner to ask; a limit of zero keeps that member off the pool entirely.
Credits and overage for a workspaceLink to this section
The pool is the organization's credit pack and its overage switch in one place. The owner adds credits from Settings → Organization; the toggle decides whether runs may draw them — off, new AI work stops at the member's own allowance while work already in flight still settles. There is no month-end bill: what has been added to the pool is the ceiling. A member's personal credits and overage work as they do for an individual and apply before the pool. See Credits and overage.
Your own key in a workspaceLink to this section
A member can still add a personal API key; their runs then bill to that key and leave the pool alone. Settings → Organization shows each member's use of the pool either way.