> ## Documentation Index
> Fetch the complete documentation index at: https://hebno.com/docs/llms.txt
> Use this file to discover all available pages before exploring further.

> ## Agent Instructions
> Hebno is a B2B AI control platform for growing teams (30-250 people). Use British English (organisation, not organization).
> Describe only what Hebno supports today. If unsure, say so.
> Spend limits use the organisation display currency in the app.
> Start with /index and /getting-started/quickstart for Hebno orientation.

# Set limits

> Create hard and soft spend limits at organisation, team, member, and project scope in Admin.

Limits cap AI usage spend within each UTC calendar month. Configure them under **Admin → Limits**.

## Open Limits

1. Sign in as **admin** or **owner**.
2. Open **Admin** from the sidebar.
3. Select **Limits**.

The page lists existing limits with current spend versus cap, enforcement mode, and scope.

## Create a limit

1. Click **Set limit**.
2. Choose **scope**: organisation, team, member, or project.
3. Select the target entity (team, member, or project) when scope is not organisation.
4. Enter the limit amount in your organisation's **display currency**.
5. Choose enforcement:
   * **Hard** - block requests when the cap is reached
   * **Soft** - alert only
6. Set **alert threshold** percentage (for example, 80% to warn before the cap).
7. Save.

Hebno validates hierarchy rules when you save team or member limits. If child limits would exceed a parent, the save is rejected with a clear error.

## Hard limit behaviour

When spend for the period meets or exceeds a hard limit:

* New chat requests are blocked with an error
* No model call is made
* Admins receive notifications

Members already mid-stream may complete an in-flight response; the block applies to the next request.

## Soft limit behaviour

Soft limits never block. They trigger notifications at the alert threshold and again at 100%.

Use soft limits for visibility on individuals or projects where you want warnings before considering a hard cap.

## Practical patterns

| Scenario                 | Suggested setup                  |
| ------------------------ | -------------------------------- |
| Agency monthly AI budget | Organisation hard limit          |
| Client delivery cap      | Team hard limit per client team  |
| Junior staff guardrail   | Member soft limit with 80% alert |
| Fixed-fee project        | Project hard limit               |

## Reserve

After assigning team and member limits, check **Reserve** on organisation and team rows. Reserve is headroom not yet allocated to child limits.

## Edit and remove

Admins can update limit amounts, enforcement mode, and thresholds. Changes apply to the current period's checks immediately.

Removing a limit stops future enforcement for that scope; past usage is unchanged.

## Next steps

* [Spend and limits](/docs/concepts/spend-and-limits) - periods, hierarchy
* [FAQ](/docs/help/faq) - blocked by limit troubleshooting