Per-member spend cap
Limit how many AI credits any single member of your organization can use per billing period, so one person can't spend the whole shared pool.
What it does
Your organization's AI credits are a shared pool. By default, any member can draw from all of it. A per-member spend cap sets a ceiling on how much a single member can use per period. Once a member reaches the cap, their AI actions pause until the period resets. Other members are unaffected, and the organization's overall credit balance still applies on top.
The default: no cap
There is no per-member cap unless an admin sets one. Members share the full pool.
Setting a cap
Org admins set the cap in Settings → Billing → AI credits, in the Per-member spend cap control:
- Choose a cap in credits: 50, 100, 250, 500, or a custom number.
- Or choose No cap to let members share the whole pool (the default).
The cap counts a member's successful AI usage since the start of the current billing period, and resets when the period does. It counts the pending action's cost too, so a member is stopped before going over, not after.
FAQ
Who can change this setting? Only organization admins. Members see the current cap read-only.
What happens when a member hits the cap? Their AI actions pause with a message explaining they've reached their limit. They can ask an organization admin to raise the cap, or wait for the next billing period.
Does the cap change my total credits? No. The cap only limits per-member usage within your existing pool. Your organization's total included credits and any overage or prepaid credits work exactly as before.
What does a cap of 0 mean? Members cannot spend any credits on AI actions. Use it to pause AI usage for everyone except admins acting through service integrations.
How is a member's usage measured? By the credits their successful AI actions consumed since the current period started. It is the same figure the admin usage breakdown shows.