Usage Limits
Usage limits let workspace admins control how many credits each team member can consume per month. This prevents a single user or team from unexpectedly draining the workspace's credit balance.
Setting a per-user limit
- Go to Settings → Billing → Usage limits.
- Find the team member you want to limit in the user list.
- Click Set limit next to their name.
- Enter the maximum number of credits they can use per month.
- Click Save.
The limit takes effect immediately. If the user has already used more credits than the new limit this month, they will be blocked from running further AI operations until the month resets.
Setting a team-wide default
You can set a default monthly credit limit that applies to all new members automatically:
- Go to Settings → Billing → Usage limits.
- Click Set default limit.
- Enter the default credit amount.
- Click Save.
Individual per-user limits override the team-wide default for specific members.
Admins are not subject to usage limits — their usage is governed by the workspace's overall credit balance, not individual caps.
What happens when a limit is reached
When a user reaches their monthly credit cap:
- Their next AI operation returns a "Credit limit reached" error.
- In-progress operations (e.g. a bulk job that is already running) complete normally — limits are checked at the start of new operations only.
- The user sees a notification explaining they have hit their limit and suggesting they contact their admin.
Viewing per-user usage
Admins can see how many credits each team member has consumed this month in Admin → Usage. The table shows:
| Column | Description |
|---|---|
| Member | Name and email |
| Credits used | Total consumed this month |
| Limit | Their monthly cap (or "Unlimited" if none set) |
| % of limit | A visual usage bar |
Usage data is updated in near real time but may lag by a few minutes during peak usage periods. If a user claims they hit their limit unexpectedly, allow a few minutes for usage to fully sync before adjusting the cap.
Raising a limit mid-month
If a user needs more credits before the monthly reset, an admin can raise or remove their limit at any time in Settings → Billing → Usage limits. Changes take effect immediately.
Per-feature operation quotas
Separately from credit caps, some AI features have daily and monthly operation quotas — a maximum number of times the operation can run, regardless of how many credits you have. These protect against a single feature (or a compromised API key) draining your allocation in a burst.
The default per-feature quotas (covering agent runs, standard and deep research, bulk processing, text-to-speech, speech-to-text, and OCR), expressed as a cap per day and per month.
Higher plans raise these quotas — for example, Professional applies a multiplier and Enterprise is effectively unlimited. When a quota is reached, the operation returns a "Quota exceeded" response until the daily or monthly window resets.
The exact default quotas and per-plan multipliers can change, so they are not hard-coded here. The quotas that apply to your workspace are visible in Settings → Billing; contact support@hubrix.ai if you need them raised.
There are therefore two independent limits on AI usage: your credit balance (and any per-user credit cap) and these per-feature quotas. An operation must pass both to run.
Credit alerts
To avoid surprises, Hubrix sends credit alerts as your workspace consumes its monthly allocation — at 50%, 80%, 95%, and 100%. Each threshold notifies admins once per billing period, so you get advance warning before credits run out rather than discovering it mid-operation.
Was this helpful?