Skip to main content
Spend and limits let admins see who and what is using Hebno, and set boundaries that block or flag usage before it passes an agreed amount. Amounts display in the organisation’s display currency, set under Admin → Settings.

​
Spend attribution

Every request records who made it, which team and project it was tagged to, which model answered, and which conversation it belongs to. That record drives three views: Tag chats to a project and a team when you start them. Untagged work still counts toward the organisation and the member, but cannot count toward a team or project limit.

​
Hard and soft limits

Only hard limits block. Before each request, Hebno checks every hard limit that applies to the organisation, the member, the team and the project. If any one is at or over its amount, the request is blocked and the member is told which limit applies.

​
Scopes

A single request counts toward every scope it touches. Work by one member, tagged to a team and a project, counts toward all four.

​
Monthly period

Limits use the UTC calendar month. Usage resets at 00:00 UTC on the first day of each month. The member view shows the reset date under Limits reset on.

​
Set a limit

1

Open Limits

Go to Admin → Limits and select Set budget limit.
2

Choose the scope

Pick Whole organisation, Team, Member or Project, then select the target.
3

Set the amount and mode

Enter the Monthly limit and choose Hard or Soft.
4

Set the alert threshold

Enter Alert at (%), from 1 to 100, and add an optional note. Save the limit.
The Reserve column shows how much of a parent limit remains to allocate. Team limits cannot add up to more than the organisation limit, and member limits cannot add up to more than their team’s limit (or the organisation limit for a member with no team limit). To change a limit, use Update limit and add a reason, which is recorded in Admin → Logs. Remove limit lifts the cap.

​
Thresholds and alerts

Each limit has an alert threshold. Alerts fire once per crossing in each period. For a hard limit, the reached alert adds that new requests are now blocked. See Notifications to change your own delivery.

​
Agent spend caps

An agent has its own Spend cap on its form, separate from budget limits. When an agent’s runs reach the cap, Hebno pauses the agent and notifies its owner with An agent reaches its spend cap. Leave the field blank for no cap. Follow-up chat inside an agent’s run conversations counts toward the cap. Resume the agent from its page after raising or removing the cap.

​
Example

An organisation sets a hard limit on the whole organisation, a hard limit on the Private Equity team, a soft limit with an 80% alert on a contractor, and a hard limit on the Target Due Diligence project. Work tagged to both the team and the project counts toward the project, team and organisation totals. The contractor is alerted at 80% and continues working, unless one of the hard limits is reached.

Limits

Create, edit and remove limits.

Agents

Set a spend cap on an agent.

Organisations, teams and members

How teams drive attribution.

Logs

Review limit changes.