> For the complete documentation index, see [llms.txt](https://infronai.gitbook.io/docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://infronai.gitbook.io/docs/features/team-budgets.md).

# Team Budgets

Control spending at the team, member, and API key levels.

Team budgets help administrators prevent unexpected inference costs while giving individual members and applications appropriate spending limits.

## How budgets work

Infron evaluates budgets at three levels:

```
Team budget
└── Member budget
    └── API key budget
```

A request must satisfy every applicable hard limit. A lower-level budget never overrides a higher-level budget.

For example, an API key with an unlimited key budget is still blocked if its member reaches a hard limit or the team exhausts its budget.

## Budget levels

### Team budget

The team budget controls the total billable usage for the entire team. It is always a hard limit.

When the team budget is exhausted, Infron blocks new billable requests for the entire team, even if individual members or keys still have available budget.

Only admins can set or change the team budget.

### Member budget

A member budget controls the combined billable usage generated by that member's personal API keys.

Admins can configure a member budget as soft, hard, or unlimited. A member cannot change their own member-level budget.

### API key budget

An API key budget controls billable usage for one key.

* Admins can manage budgets for team-level and admin keys.
* Members can manage budgets for their own personal keys.
* Billing managers can view budget information but cannot change it.

## Budget modes

| Mode          | Behavior                                                                | Available for                     |
| ------------- | ----------------------------------------------------------------------- | --------------------------------- |
| **Soft**      | Sends alerts when the limit is reached but continues allowing requests. | Member and API key budgets        |
| **Hard**      | Blocks new billable requests when the limit is reached.                 | Team, member, and API key budgets |
| **Unlimited** | Does not apply a limit at this level. Higher-level limits still apply.  | Member and API key budgets        |

Team budgets always use hard enforcement.

### Soft limits

A soft limit is useful when you want visibility without interrupting workloads.

When a member exceeds a soft limit, Infron alerts that member but continues processing their requests. When a key exceeds a soft limit, Infron alerts the key holder.

### Hard limits

A hard limit prevents additional billable usage at its level:

* A hard key limit blocks that API key.
* A hard member limit blocks billable requests for that member.
* The team hard limit blocks billable requests for the entire team.

A member hard limit does not block that member's BYOK requests.

## Example

Assume a team has the following monthly budgets:

```
Team: $10,000 hard
Alice: $2,000 soft
Alice's test key: $500 hard
```

The results are:

* At $500, the test key is blocked because it reached its hard key limit.
* At $2,000 of total usage, Alice receives an alert but her other keys continue working because her member limit is soft.
* At $10,000 of total team usage, all new billable requests for the team are blocked.

## Setting a team budget

To set the team's total budget:

1. Switch to the team you want to manage.
2. Open **Team Settings**.
3. In **Team budget**, select **Set budgets**.
4. Enter the limit and choose its reset period.
5. Save the budget.

Only team admins can change the team budget.

## Setting a member budget

To set a budget for a member:

1. Open **Team Members**.
2. Select the member.
3. Open the member's actions menu.
4. Select the budget action.
5. Choose **Soft**, **Hard**, or **Unlimited**.
6. If required, enter the limit and reset period.
7. Save the budget.

Only admins can change member budgets.

## Setting an API key budget

To set a budget for an API key:

1. Open **API Keys** in the active team.
2. Select the key you want to manage.
3. Open its budget settings.
4. Choose **Soft**, **Hard**, or **Unlimited**.
5. If required, enter the limit and reset period.
6. Save the budget.

Members can perform this action only for their own personal keys. Admins can manage team and admin key budgets.

## Budget periods and resets

Budget usage resets at the beginning of the configured period. All reset times use UTC.

| Period      | Reset time                                |
| ----------- | ----------------------------------------- |
| **Daily**   | Every day at 00:00 UTC                    |
| **Weekly**  | Every Monday at 00:00 UTC                 |
| **Monthly** | The first day of every month at 00:00 UTC |
| **Yearly**  | January 1 every year at 00:00 UTC         |

Infron displays dates and times in your local timezone where applicable, but enforcement uses UTC.

## Budget alerts

Infron sends alerts as usage approaches a configured budget.

| Budget or balance | Thresholds             | Recipients                                            |
| ----------------- | ---------------------- | ----------------------------------------------------- |
| **Team**          | 50%, 80%, and 100%     | Admins by email and a dashboard banner                |
| **Member**        | 50%, 80%, and 100%     | The member by email; admins are also notified at 100% |
| **API key**       | 50%, 80%, and 100%     | The key holder by email                               |
| **Low balance**   | Team-defined threshold | Admins and billing managers                           |

An alert does not necessarily mean requests are blocked. Blocking depends on whether the applicable budget uses soft or hard enforcement.

## Permissions

| Action                             | Admin | Member | Billing manager |
| ---------------------------------- | ----- | ------ | --------------- |
| View team budget information       | Yes   | No     | Yes             |
| Change the team budget             | Yes   | No     | No              |
| Change member budgets              | Yes   | No     | No              |
| Change team or admin key budgets   | Yes   | No     | No              |
| Change own personal key budgets    | Yes   | Yes    | No              |
| Manage top-ups and payment methods | Yes   | No     | Yes             |

## Frequently asked questions

<details>

<summary>What happens if multiple budgets are exceeded?</summary>

Infron enforces every applicable hard limit. If the team budget is exhausted, the entire team is blocked regardless of the member or key budget.

</details>

<details>

<summary>Does unlimited mean there is no spending limit?</summary>

Only at that specific level. An unlimited key still follows its member budget and the team budget. An unlimited member still follows the team budget.

</details>

<details>

<summary>Does a soft limit stop requests?</summary>

No. Soft limits generate alerts but continue allowing requests.

</details>

<details>

<summary>Do hard member limits block BYOK usage?</summary>

No. A member hard limit blocks billable Infron usage but does not block that member's BYOK requests.

</details>

<details>

<summary>Who can increase a blocked member's budget?</summary>

A team admin can update the member budget or change its mode. Members cannot override a budget assigned by an admin.

</details>


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://infronai.gitbook.io/docs/features/team-budgets.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
