> For the complete documentation index, see [llms.txt](https://docs.artific.nl/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.artific.nl/en/for-administrators/organization/budgets.md).

# Budgets

Putting a ceiling on what AI usage may cost. The organisation total is set under **Organization management → Budgets**; a budget for one assistant on the **Budget** tab of that assistant's settings.

## Why set a budget

Assistants that work on their own through [triggers](https://docs.artific.nl/en/for-administrators/assistants/triggers.md) keep using AI whether or not anyone is watching. A budget keeps costs predictable: you are told in time when usage rises, and if you choose, usage stops at an amount you set.

## Two kinds of budget

| Budget                 | Applies to                                       | Where                                 |
| ---------------------- | ------------------------------------------------ | ------------------------------------- |
| **Organisation total** | All AI usage in your organisation.               | **Organization management → Budgets** |
| **Assistant budget**   | One assistant, on top of the organisation total. | The assistant's **Budget** tab        |

Budgets apply per calendar month and are set in dollars.

## What a budget consists of

At the top you see **Usage this month**, against the stop limit if one is set.

### Stop limit

The emergency brake. Switch on **Stop everything at** and enter an amount per calendar month. When usage reaches it:

| Budget                 | What stops                                                                                          |
| ---------------------- | --------------------------------------------------------------------------------------------------- |
| **Organisation total** | All AI usage in the organisation.                                                                   |
| **Assistant budget**   | This assistant stops answering chats and running tasks. The rest of the organisation keeps working. |

Everyone your alerts notify receives an e-mail when a stop limit is reached.

### Alerts

An alert sends an e-mail as soon as usage reaches an amount. Alerts are independent of the stop limit: they never stop anything.

Choose **Add alert**, enter the amount, and choose who receives the e-mail. A budget can have several alerts, and each alert can go to several users or user groups. To choose recipients you need rights to view users or user groups.

**Save changes** applies everything on the page.

## After a stop

Usage resumes automatically on the first day of the next calendar month. To resume sooner, an administrator raises the stop limit.

While a budget is used up:

* assistants reply that the message could not be answered because the budget is used up,
* runs stop, and show the budget as the reason in the [Cockpit](https://docs.artific.nl/en/for-administrators/assistants/runs.md),
* scheduled quality control does not start; the next scheduled run tries again.

{% hint style="warning" %}
A stop limit stops usage the moment it is reached, also in the middle of the working day. Agree the amount in advance with the people who depend on the assistants.
{% endhint %}

## Setting budgets sensibly

* **Start with alerts, not a stop limit.** Two alerts, for example at half and at four-fifths of what you expect to spend, show you how usage develops before anything stops.
* **Give assistants that run on their own an assistant budget.** A trigger with an instruction that turns out more expensive than expected is then contained, while the rest of the organisation keeps working.
* **Send alerts to a group**, not to one person, so someone sees them when a colleague is away.
* **Revisit the amounts** once you have a few months of usage. The [Token report](https://docs.artific.nl/en/for-administrators/reports/tokens.md) shows where the cost goes.
