Organization Usage Limits allow you to define consumption limits that apply to the entire Organization. These limits control the maximum usage that can be consumed across all Projects within that Organization.
The Organization consumption is the real, aggregated usage of all its Projects, plus any usage charged directly to the Organization. A Project limit does not reserve any amount from the Organization budget.
A usage limit defines two thresholds:
- Soft limit alert, which triggers a notification when the defined usage threshold is reached.
- Hard limit alert, which defines the maximum allowed usage.
When the Hard limit alert is reached, the platform prevents additional requests from being executed.
Limits can be configured using different subscription types, such as Freemium, Daily, Weekly, or Monthly. Depending on the configuration, the limit may renew automatically after each period.
To access and configure Organization Usage Limits, you must have the System Administrator role, which grants access to SuperAdmin Options in the Console.
To manage usage limits for an Organization:
- Open the Console.
- In the Console Menu, go to Superadmin Options.
- Select Organizations.
- Use the search field to locate the desired Organization. You can configure the filter using one of the following options:
- Contains: Searches for Organizations whose name contains the entered term.
- Starts with: Filters Organizations whose names begin with the entered text.
- Click USAGE LIMITS for the selected Organization.
This opens the Usage Limit (Organization) page, where you can view existing limits or create new ones.
The Usage Limit (Organization) page displays all limits defined for the Organization.
Each record includes the following information:
- Valid until: Date when the limit expires.
- Status: Current state of the limit. Possible values include:
- Active: The limit is currently applied and usage is still available.
- Expired: The defined time period has ended.
- Empty: The Hard limit alert has been reached.
- Cancelled: The limit has been manually cancelled.
- Type: Subscription type used for the limit (Freemium, Daily, Weekly, or Monthly).
- Renewable?: Indicates whether the limit automatically renews after the defined period.
- Unit: Measurement unit used to calculate consumption. For Organizations, this can be Cost (USD) or Tokens. Requests is available only for Project limits.
- Hard limit alert: Maximum usage allowed for the Organization.
- Remaining: Remaining usage available before reaching the Hard limit alert, calculated from the real aggregated consumption of all Projects.
To create a new usage limit, click CREATE NEW.
The Usage Limit configuration page opens.
On this page, you can configure the following fields:
- Entity Name: Indicates the entity to which the limit applies (Organization).
- Status: Current status of the limit.
- Subscription type: Defines the usage period (Freemium, Daily, Weekly, or Monthly).
- Unit: Defines the metric used to measure consumption (Cost (USD) or Tokens).
- Soft limit alert: Usage threshold that triggers a notification.
- Hard limit alert: Maximum allowed usage for the Organization.
Click CONFIRM to create the limit or CANCEL to discard the configuration.
Once a quota is created using the CREATE NEW button, two additional options become available:
- UPDATE: Allows you to modify the parameters of the active quota.
- CANCEL: This option allows you to cancel the active quota, enabling the creation of a new limit.
Note: To update an existing quota, the new Hard limit alert value must be greater than the previous value. For example, if the previous Hard limit was 300, the updated value must be greater, such as 350 or 400.
When an Organization has an active quota, its Projects must measure the same thing on the same schedule.
- Project limits must use the same Unit as the Organization limit.
- Project limits must use the same Subscription type as the Organization limit.
- Organizations are never measured in Requests. Only Cost (USD) and Tokens are available for Organization limits.
Because the Organization and its Projects share the same Unit and Subscription type, they renew together. Their periods stay aligned from one period to the next, so the aggregated consumption remains consistent.
If a Project quota does not match the Unit or the Subscription type of the Organization, the platform blocks the definition of the Organization limit and shows an alert listing the affected Projects. You must change or cancel those Project quotas before the Organization limit can be defined.
- The Organization limit acts as a maximum cap on the real combined usage of all Projects, not on the sum of the quotas assigned to them.
- Project limits may add up to more than the Organization Hard limit alert. For example, if the Organization limit is 100 and Project A and Project B each have a limit of 80, the total of Project limits is 160, which is allowed. If Project A consumes 60 and Project B consumes 45, each Project still has individual balance available, but the Organization total is 105. The next request from either Project is blocked.
- A Project quota is an individual maximum limit, not a guarantee of availability. A request can be blocked by the Organization limit even when the Project still shows remaining balance.
- If an Organization limit is defined for Projects without quotas, those Projects use the Organization account balance.
- Cancelling a quota does not credit anything back to the Organization. The usage already consumed stays counted, and cancelling only prevents further consumption under that quota.
- The Organization consumption shown in the Console and in the Usage Dashboard reflects real usage, updated as Projects consume. No amount is locked away unused.