Cost Control
Control and monitor Compute Block (CB) usage across your organization. Set limits per user, group, API key, or bot; validate cost centers; and manage extended-usage requests from one admin panel.

What you can do
Setting Limits
Default limit, reset time, overrides for users, groups, API keys and public bots, limits users set on their own API keys
When a Limit Is Reached
Warnings before the limit, the limit popup and banner, the pre-check before a request, letting users continue with a project code, cost center validation, the Project Codes list
Monitoring Usage and Cost
Usage in the user profile, the Session Meter in chat, Compute Block pricing, Usage Export
How limits stack
When more than one limit could apply to a user, the most specific one wins:
Per-user override: always wins.
Group limit: applies to members of a limited group. If a user is in several limited groups, the most generous one applies, unless you choose to add group limits up (see Setting Limits).
Default limit: the baseline for everyone else.
API key limits and bot limits run separately from this order.
Who can do what
Access to cost control is set with permissions. By default, admins and super admins have all of them, except that only super admins see real names in usage reports.
Manage cost controls
Configure limits (default, users, groups, API keys), warning thresholds, the limit messages, and turn Compute Block Limits on or off
View usage reports
See the consumption and usage reports in Analytics
View real user names and emails in usage reports
See real names and email addresses in usage reports. Without it, reports show every number, but users appear as their user ID and emails are masked.
Export usage events
Download the Usage Export. The export always includes names and emails.
Glossary
Compute Block (CB)
The unit that measures resource consumption on the platform. Every action, such as sending a chat message or uploading a file, consumes a defined number of CBs.
CB Limit
The maximum number of Compute Blocks a user may consume within a given timeframe.
Timeframe
The period over which CB consumption is counted and reset: Daily, Weekly, or Monthly.
Reset time
The time of day a Compute Block day begins. Midnight unless an admin sets another time.
Hard Limit
Once the CB limit is reached, no further CB-consuming actions are possible until an admin increases the limit. The user cannot self-service.
Soft Limit
Once the CB limit is reached, the user can enter a project code or cost center to add a preset amount of extra Compute Blocks and keep working. The extra usage is attributed to that code and expires after a set period.
Default Limit
An organization-wide CB limit that applies to all users unless an override is set.
Group Limit
A CB limit applied to an entire Active Directory (AD) group, setting the same allowance for all members at once.
API Key Limit
A CB limit on one API key, set by an admin or by the key's owner.
Bot CB Limit
A CB cap on an individual public bot. Interactions with a capped bot are charged against the bot's own pool, not the user's personal allowance.
Cost Center / Project Code
An optional numeric label a user can enter so their usage can be attributed to an internal cost center, project, or case number (Aktenzeichen) for reporting.
Extended Usage Amounts
The admin setting that lets users request extra Compute Blocks beyond their limit. On means soft limit, off means hard limit.
Usage Warning
A one-time, dismissable banner and/or email that appears before the limit is reached.
Session Meter
The counter in the chat header that shows how many Compute Blocks the current chat has used, and optionally an estimated cost.
Price per 1M Compute Blocks
The price an admin sets so users can see an estimated cost of their usage. It is an estimate, not an invoice.
Last updated

