--- title: Usage Management description: Monitor team-wide AI Units consumption from Olly and cap it with limits set per user, per user group, or per API key so no one depletes the team quota. url: https://coralogix.com/docs/user-guides/olly/usage-management/ product: ai feature: Olly feature_id: olly feature_identifier: ai/olly last_updated: '2026-11-10' --- # Usage Management **Usage Management** shows your team's [AI Units](https://coralogix.com/docs/user-guides/account-management/payment-and-billing/ai-units-pricing.md) consumption on Olly in the current billing cycle. Anyone on your team can open it to see team-wide, per-user, and per-API-key spending. Admins can cap consumption with monthly limits set per user or per user group, and cap the AI Units each Olly-enabled API key consumes, to prevent any one user or API key from depleting the team's shared quota and to even out usage across the team. ## What you need * Olly turned on for your team. See [Enable Olly](https://coralogix.com/docs/user-guides/olly/enable.md). * An AI units budget. Coralogix sets your team's [AI units](https://coralogix.com/docs/user-guides/account-management/payment-and-billing/quota-rules.md#cx-units-and-ai-units) at provisioning, as a pool separate from the CX units your data uses. Teams provisioned before the AI units split use an allocation on the `olly` entity type instead (see [Allocate units to Olly](#allocate-units-to-olly)). * The [`OLLY-USAGE:MANAGE`](https://coralogix.com/docs/user-guides/aaa/access-control/permissions/permissions-list.md) permission to set or reset limits. See [Permissions](#permissions) for what this permission allows. Viewing the screen doesn't require it. ### Allocate units to Olly If your team has an AI units budget, it appears as its own **AI units** section in **Quota Rules** and there's nothing to allocate. On teams provisioned before the AI units split, the `olly` entity type starts as **Unallocated**. To give the Usage Management screen a quota to track on those teams: 1. Open **Data Flow**, then **Quota Rules**. 2. In **Allocations by entity type**, search for `olly`. 3. On the `olly` row, enter a value in the **Allocation** column (as **Percentages** or **Units**), then select **Allocate** in the **Status** column. 4. Select **Save**. Once the rule is active, the Usage Management screen reads the allocation and shows progress against it. For the full Quota Rules workflow, see [Quota Rules](https://coralogix.com/docs/user-guides/account-management/payment-and-billing/quota-rules.md). ## Open Usage Management In Coralogix, select **Olly AI** in the navigation bar, then **Usage Management**. The screen has two parts: * The **Monthly team quota** bar and the **Team Overview** card summarize team-wide consumption and what remains this month. * The **Users**, **Groups**, and **Automations & Agents** tabs break usage down: **Users** lists every team member with their groups, usage, effective limit, and status; **Groups** lists your team's user groups so you can limit everyone in a group at once; **Automations & Agents** lists your team's Olly-enabled API keys (including the keys that automations run as) so you can limit each one. ## View team-wide Olly usage The **Monthly team quota** bar shows how much of the team's monthly AI Units allocation the team has consumed so far this month. Olly and AI Center draw on the same allocation, so the bar stacks both: Olly usage first, then AI Center usage, with a legend that tells them apart. The usage percentage and the `used / total` units next to the bar count both products. To request a higher allocation, talk to your account manager or Coralogix Support, or select **Upgrade**. [![The Monthly team quota bar in Usage Management, with Olly and AI Center usage stacked against the allocation, and the Team Overview card showing Total spent this month and Remaining this month](/docs/assets/images/usage-management-monthly-team-quota-491f2f125b0ad7546a7aaf26f82cbf4c.webp)](https://coralogix.com/docs/assets/images/usage-management-monthly-team-quota-491f2f125b0ad7546a7aaf26f82cbf4c.webp) The **Team Overview** card breaks down this month's Olly usage: * **Total spent this month**: The AI Units the team has consumed on Olly this month, with the share of the monthly allocation it represents. AI Center usage isn't included. * **Remaining this month**: The monthly allocation minus the team's Olly usage, with the share remaining, until the next reset. AI Center usage isn't subtracted, so this value can be higher than what the quota bar shows as left. ## Set a per-user monthly limit A per-user limit caps how many AI Units a team member can consume on Olly in the current billing cycle. When a user reaches their limit, they can't use Olly until the cycle resets. To set a limit for one user: 1. On the **Users** tab, find the user row. 2. Select **Edit limit**. 3. In **New limit value (units)**, enter a value within the displayed range. 4. Select **Apply**. The new limit takes effect immediately. To set the same limit on several users at once: 1. On the **Users** tab, select the check box in each user row you want to update. 2. Select **Set usage limit**. 3. In **New limit value (units)**, enter a value within the displayed range. 4. Select **Apply**. ## Set a per-group monthly limit A group limit caps how many AI Units every member of a Coralogix user group can consume on Olly in the current billing cycle, without setting each member individually. It applies to group members who have no per-user limit of their own. Manage which users belong to a group in [Groups](https://coralogix.com/docs/user-guides/account-management/user-management/assign-user-roles-and-scopes-via-groups.md). To set a limit for a group: 1. On the **Groups** tab, find the group row. 2. Select **Set Limit**. 3. In **New group limit (units)**, enter a value within the displayed range. 4. Select **Apply**. The **Groups** tab shows each group's member count and current monthly limit. To remove a group's limit, open the more actions menu in the group's row and select **Clear limit**. When a user belongs to more than one group that has a limit, the highest (most permissive) group limit applies. To find the users a group limit affects, use the group filter on the **Users** tab. The **Groups** column there shows each user's group memberships. ## Set a limit for an API key The **Automations & Agents** tab lists your team's Olly-enabled API keys, including the team API keys that automations run as, such as the key created by [automatic case analysis](https://coralogix.com/docs/user-guides/olly/automatic-case-analysis.md). Each key appears as a card with its name, key ID, monthly AI Units usage, and status, and stays listed whether or not it has consumed any units. Use **Search API keys** to filter the list by name or key ID. A limit caps how many AI Units a key can consume on Olly in the current cycle: * A key with a limit shows its usage against that limit (a percentage and a `used / total units` bar) and its footer reads **Custom limit** or **Default limit**. * A key with no limit shows only the units it has used and is marked **Unlimited**. To set a limit for one key: 1. On the **Automations & Agents** tab, find the key's card. 2. Select **Edit limit**. 3. In **New limit value (units)**, enter a value within the displayed range. 4. Select **Apply**. The limit takes effect immediately. To apply one limit to every key without a custom limit, select **Set default monthly limit** at the top of the tab. To clear a key's custom limit so it falls back to the default, open the more actions menu on the key's card and select **Reset to default limit**. A key's status badge reflects its usage against its effective limit. The custom limit when set, otherwise the default. A disabled key is dimmed and marked **Disabled**. ## How the effective limit is chosen Only one limit applies to a user at a time. Coralogix uses the most specific limit that exists, in this order: 1. **Per-user limit**: an explicit limit set for that user. Overrides every other level. 2. **Group limit**: applies when the user has no per-user limit. If the user is in several groups that have limits, the highest one applies. 3. **Team default limit**: applies when the user has neither a per-user nor a group limit. 4. **Team allocation**: when no limit is set at any level, the user is capped only by the team's overall AI Units allocation. On the **Users** tab, each row indicates which of these applies to that user, a per-user limit, a group limit and the group it comes from, or the team default. ## Reset a user limit to the team default Resetting clears a user's per-user limit so their effective limit falls back to the next level that applies, a group limit, then the team default, then the team's overall AI Units allocation. See [How the effective limit is chosen](#how-the-effective-limit-is-chosen). 1. On the **Users** tab, open the more actions menu in the user's row. 2. Select **Reset to default limit**. ## Status badges Each user row carries a status badge that reflects their position against the effective limit, the per-user limit when present, otherwise a group limit, otherwise the team default, otherwise the team's overall AI Units allocation. See [How the effective limit is chosen](#how-the-effective-limit-is-chosen). | Badge | Meaning | | ------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | | OK | Usage is under 70% of the effective limit. | | Approaching | Usage has reached 70% of the effective limit but is still under the limit. | | Limit reached | Usage has reached or exceeded the limit. The user can't use Olly until the next cycle. A user whose effective limit is **0** is locked out from the start of the cycle, raise their limit in **Edit limit** to restore access. | Use the status filter in the table header to narrow the list to one or more statuses. ## What users see as a limit approaches The **Approaching** badge is your early signal as an admin, from 70%. Users get their own warning later and closer to the limit: once consumption reaches 90% of a monthly quota, Olly shows an alert in the chat naming the threshold they reached and pointing them to an admin to raise the limit. This is why users contact you before they are blocked rather than after. * **Two thresholds**: 90% and 95%. The warning names the highest threshold reached, never the exact usage, so a user at 97% sees the 95% warning. * **Two scopes**: the user's own effective limit, or the team's shared quota. Only one warning appears at a time, for whichever is closer to its quota, and the message names which limit needs raising. If both are equally close, the personal one wins. * **No limit, no warning**: a scope with no monthly limit never warns, because there is nothing to approach. * **Dismissible**: closing the warning hides it for the current chat only. It returns if the user reaches 95%, or if the other scope becomes the closer one. * **Refreshed every minute**: Olly rechecks usage about once a minute while the chat is open, so a limit you raise clears the user's warning without them reloading. Once a limit is reached, this warning gives way to the blocking message and the user can't send messages until the next cycle or until you raise their limit. ## Permissions What you can do on the screen depends on whether you hold the [`OLLY-USAGE:MANAGE`](https://coralogix.com/docs/user-guides/aaa/access-control/permissions/permissions-list.md) permission. Viewing is open to everyone. Only admins can change limits. | Capability | Any user | Admin (`OLLY-USAGE:MANAGE`) | | -------------------------------------------- | -------- | --------------------------- | | See team-wide consumption | Yes | Yes | | See each user's usage and status | Yes | Yes | | See API key usage | Yes | Yes | | Set the team default limit | No | Yes | | Set per-user monthly limits (single or bulk) | No | Yes | | Set per-group monthly limits | No | Yes | | Set a limit for an API key | No | Yes | | Reset a user limit to the team default | No | Yes | ## Next steps Learn how Olly processes and protects your data in [Data processing, privacy, and compliance](https://coralogix.com/docs/user-guides/olly/data-privacy.md).