Overview
The monthly AI consumption caps, their scopes and what happens when they are exceeded.
Quotas sets the monthly caps on AI model consumption. With no cap configured, a scope consumes without limit.
The same screen exists in two places, Organization › Quotas and Workspace › Quotas, with different scopes and identical behavior.
The scopes
The two tabs at the top switch between Organization and Workspace. Within each there are breakdowns:
- General: that scope's total cap.
- Providers: one cap per provider, for when one of them is more expensive than the others.
- Users: how much each person can consume.
- Project keys: only in the workspace scope, for programmatic integrations.
The Project keys tab exists because an integration consumes differently from a person: nonstop, and often with no one watching.
The Organization quota takes precedence over the Workspace quota. Once the company's cap is used up, no workspace continues, however much headroom it has under its own limit.
Who changes them
In the organization, the screen opens for Superadmin, Admin and, read-only, Auditor. In the workspace, for Owner, Curator and Auditor, but only the Owner saves changes.
Exceptions per person and per key
On the Users and Project keys tabs you can create exceptions for individual cases, on top of the default cap.
An exception overrides that scope's default cap for that person or key. Unlike a temporary grant, it doesn't expire on its own. The action menu lets you edit it, grant temporary headroom or remove it.
What happens when a cap is exceeded
The call is refused and whoever is in Chat gets a quota-exceeded warning. The platform doesn't switch models or degrade the answer.
The block applies only to the scope that went over. A person who hit their own limit can no longer use the platform, while the rest of the workspace carries on.
Caps apply to the current month. The turn of the month resets accumulated consumption and unblocks automatically.