> ## 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 an AI work platform for client research and delivery: chat, research runs with sources, deliverables (Word, PowerPoint, Excel, email), projects, a shared library, agents, Office add-ins, and integrations with Microsoft 365, Google Workspace, CRM, project delivery, ERP and finance systems.
> Use British English (organisation, not organization).
> Every feature and integration described in these docs is available. Describe it as documented.
> Hebno never writes to a connected system without a member confirming a card. Finance and ERP writes are drafts only.
> Do not discuss commercial terms. Direct commercial questions to support@hebno.com.
> Start with /index and /get-started/quickstart.

# Limits

> Set hard or soft monthly spend limits for the organisation, a team, a member or a project, and choose when admins are alerted.

Spend limits stop one team, member or project from using more than you intended in a month. A **hard** limit blocks requests at the cap. A **soft** limit alerts you and lets work continue. Find them under **Admin → Limits**.

## Limit scopes

| Scope | Applies to |
| - | - |
| **Whole organisation** | All spend in the organisation |
| **Team** | Chats tagged to that team |
| **Member** | One person, across every team and project |
| **Project** | Chats tagged to that project |

A request is checked against every limit that applies to it: the organisation, the member, the team on the chat and the project on the chat. If any **hard** limit is at or over its cap, Hebno blocks the request and shows the member why.

## Create a limit

**1. Open the form**

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

**2. Choose a scope**

Pick **Whole organisation**, **Team**, **Member** or **Project**, then select the team, member or project.

**3. Set the monthly limit**

Enter the **Monthly limit** in your organisation's display currency. The amount must be greater than zero.

**4. Choose enforcement**

Select **Hard** to block requests at the limit, or **Soft** to alert only and allow spending to continue.

**5. Set the alert threshold**

Enter **Alert at (%)**, a whole number from 1 to 100. Hebno alerts admins when spend crosses that share of the limit.

**6. Add a note**

Optionally add a **Note** explaining why the limit exists, then save.

## The limits table

The **Budget limits** table shows one row per limit.

| Column | Meaning |
| - | - |
| **Scope** | What the limit applies to |
| **Monthly limit** | The cap in your display currency |
| **Reserve** | How much of the parent limit is still unallocated |
| **This month** | Spend so far this month |
| **Enforcement** | **Hard** or **Soft** |
| **Alert at (%)** | The alert threshold |

The **Active limits** card at the top counts the limits you have configured.

## Limit hierarchy

Limits nest. The sum of team limits cannot exceed the organisation limit, and the sum of member limits cannot exceed their team's limit (or the organisation limit when the member has no team limit). When a new limit would exceed what is available, Hebno shows the available reserve so you can lower it.

**Reserve** shows how much of the parent limit you can still allocate.

## Who is alerted

| Event | Who is notified |
| - | - |
| Spend crosses the alert threshold | Every owner and admin (in the app and by email). For a member limit, that member too. |
| Spend reaches the limit | Every owner and admin. For a member limit, that member too. For a hard limit, the message says new requests are blocked. |
| A request is blocked | The member whose request was blocked |

Each alert fires once per limit per month. Members see their own limits and usage under **Usage** in the user menu.

## When limits reset

Limits measure the UTC calendar month. Usage resets at 00:00 UTC on the first day of each month, and blocked members can work again from that moment.

To restore access earlier, raise the limit or remove it. Edit a limit, change the amount, and add a reason in **Reason for change**. Select **Remove limit** to delete it: spend then continues without a cap at that scope.

## Agents and limits

Each agent has its own spend cap on the agent form. Reaching it pauses the agent and notifies its owner. Agent cap is separate from the limits on this page, but agent spend still counts toward the organisation, team and project limits that apply.

## Choose hard or soft

* Use **hard** limits where overspend has a real consequence: a fixed-fee engagement, a pilot team, an unattended agent.
* Use **soft** limits to learn what normal looks like. Set the alert at 80% and watch the [overview](https://hebno.com/docs/admin/overview.md) for a month before tightening.

Every limit change is recorded in [Logs](https://hebno.com/docs/admin/logs.md) under **Spend**.

## Next steps

* Read [Spend and limits](https://hebno.com/docs/concepts/spend-and-limits.md) for how members experience a limit.
* Create [teams](https://hebno.com/docs/admin/teams.md) to give each group its own cap.
* Review spend by team on the [overview](https://hebno.com/docs/admin/overview.md).


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.