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

# Policies — Usage

> Budgets, spend limits, repository scope and account access

|             |                                   |
| ----------- | --------------------------------- |
| **URL**     | `/policies/cost-policies`         |
| **Sidebar** | Policies → Usage                  |
| **Roles**   | Admin · Analytics Viewer, reading |

Usage policies govern what your organization spends, where work may happen, and which accounts developers may use.

## What's on the page

### Tab strip

| Tab                    | URL                          | Governs                                                    |
| ---------------------- | ---------------------------- | ---------------------------------------------------------- |
| **Budget Limit**       | `/policies/cost-policies`    | Monthly budgets and rolling spend limits                   |
| **Repositories Scope** | `/policies/repository-scope` | Which GitHub organization work is allowed in · Beta        |
| **Account Access**     | `/policies/account-access`   | Which vendor account a developer may be signed into · Beta |

### Budget Limit fields

| Field                   | What you set                                           |
| ----------------------- | ------------------------------------------------------ |
| **Monthly Budget**      | The per-user cap for the calendar month                |
| **Spend Limit**         | A per-user cap over a rolling window                   |
| **Window**              | How long that rolling window runs, in hours            |
| **Alert Threshold**     | The percentage at which a warning fires before the cap |
| **Enforced In**         | Where the limit applies                                |
| **Enforcement Message** | What the developer sees when the limit is reached      |

Spend Limit and Window are set together — they describe one rule. The alert threshold defaults to 80%, and the warning still allows the request through, so a developer gets notice before work stops. The enforcement message takes up to 500 characters.

When more than one budget policy reaches the same developer, **one of them applies** — the lowest priority number wins, and the rest are ignored. Budgets are never added together, and the stricter one does not automatically win. See [Cost Policies](/policies/cost-policies#one-budget-per-developer).

Budget blocking covers **Claude Code, Claude Cowork and Codex**. Spend limits cover those three and **Cursor**.

### Repositories Scope

Names the GitHub organization your agents may work in. A policy opens at `/policies/repository-scope/[id]`.

### Account Access

Decides which vendor account a developer may be signed into when they run a coding agent.

## Filters and controls

Every Usage policy applies organization-wide or is scoped to user groups, managed on **Users → User Groups**.

## What you can do

| Action                         | Result                                                                                                                                               |
| ------------------------------ | ---------------------------------------------------------------------------------------------------------------------------------------------------- |
| Create or open a policy        | Opens the editor for that tab                                                                                                                        |
| Open an Account Access policy  | Opens its own page at `/policies/account-access/[id]`, listing the attempts it blocked over a window you choose — last 7, 14 or 30 days, or 3 months |
| Open a repository-scope policy | Opens its own page at `/policies/repository-scope/[id]`, where incidents against it open a detail panel                                              |

## Messages you may see

| Message                                                                                    | What it means                                                                          |
| ------------------------------------------------------------------------------------------ | -------------------------------------------------------------------------------------- |
| `Failed to save policy`                                                                    | The policy was not saved. Your entries stay on screen, so saving again is enough       |
| `Failed to delete policy`                                                                  | The policy is still in place                                                           |
| `Failed to update order`                                                                   | A reordering was not stored, so priority is unchanged from what the list showed before |
| `No policies configured` · `No access policies created yet` · `No Repository Policies Yet` | Nothing of that kind exists yet — the empty state, not an error                        |
| `No policies found matching your filters` · `No policies found for this type`              | Policies exist, but none matches what you have narrowed to. Widen the filters          |
| `No models available` · `No models match your search`                                      | The model picker has nothing to offer for the current search                           |

## Related

| Page                                            | For                                        |
| ----------------------------------------------- | ------------------------------------------ |
| [Cost Management](/dashboard/cost-management)   | Spend against these limits, and exemptions |
| [Analytics — Usage](/dashboard/analytics/usage) | Account Access blocked attempts            |