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.
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. Depending on configuration, this can be Requests, Cost (USD), or Tokens.
- Hard limit alert: Maximum usage allowed for the Organization.
- Remaining: Remaining usage available before reaching the limit.
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 (Requests, 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 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). Additionally, the Soft limit and Hard limit must be equal to or greater than the sum of all Soft limit and Hard limit quotas defined per project.
- The Organization limit acts as a maximum cap for all Projects.
- When setting an Organization limit, ensure it is not lower than any existing Project limit, because Project limits cannot exceed the Organization limit.
- If an Organization limit is defined for Projects without quotas, those Projects will start using the Organization account balance.
- Projects with specific quotas will respect their limits while adhering to the Organization limits.
- The sum of all Project quotas can exceed the quota limit defined for the Organization. This is because the Organization limit represents a global cap on actual usage, not the sum of available quotas. For example, if the Organization limit is 100, Project A has a limit of 70, and Project B has a limit of 60, the total of Project limits is 130. However, in practice, the combined consumption of Projects A and B can never exceed 100. If Project A consumes its full 70, only 30 will remain available for Project B, even though its quota is 60. In summary, a Project quota is an individual maximum limit, not a guarantee of availability.