Limits vs subscription
Seat billing and AI spend limits are separate. Limits control how much model usage your organisation can incur before requests are blocked or alerts fire.
Hard vs soft
Only hard limits stop new chat requests. Soft limits are for visibility and operator notification.
When a hard limit blocks a request, the member sees an error and no model call is made.
Scopes
Set a limit on one of four scopes:
A single request is checked against every hard limit that matches the conversation’s organisation, member, team, and project tags.
Billing period
Limits reset on UTC calendar months. The period start is the first day of the month at 00:00 UTC. Reports and limit checks use the same period boundary.Hierarchy rules
When admins create limits, Hebno validates that child budgets do not exceed parents:- Sum of team limits cannot exceed the organisation limit
- Sum of member limits within a team cannot exceed that team limit
- Members not on a team: personal limits cannot exceed the organisation limit
- Project and organisation scopes skip hierarchy checks against siblings
Alerts
For each limit you can set an alert threshold (percentage of the cap). When spend crosses the threshold, admins receive notifications. At 100% of a soft limit, alerts fire again. At 100% of a hard limit, subsequent requests are blocked.Reserve
When viewing limits in admin, Reserve is the unallocated budget remaining at organisation or team level after assigned child limits. Use it to see headroom before assigning more caps.Example
An agency sets:- Organisation hard limit: €2,000/month
- Team hard limit (Client A): €800/month
- Member soft limit (freelancer): €100/month with alert at 80%
Next steps
- Set limits - admin walkthrough
- Attribution - how team and project tags affect spend roll-ups