> For the complete documentation index, see [llms.txt](https://docs.onelens.cloud/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.onelens.cloud/govern-control-and-governance/budgets.md).

# Budgets

Budgets let you plan spend for any slice of your cloud, AI and SaaS costs, compare actual cost against that plan period by period, and alert people when spend runs ahead of it.

Every budget is tied to a Report. The Report decides which costs the budget tracks. The budget adds a planned amount for each row of that Report and each period.

> Only Admins can create and edit budgets. Other users can view them.

### Where to find Budgets

Go to **Govern → Budgets**. The page has three tabs.

| Tab                | What it shows                                                                               |
| ------------------ | ------------------------------------------------------------------------------------------- |
| Manage Budgets     | Every budget with its status, type and dates. Create and open budgets from here             |
| Budget Performance | Last month's cost against last month's budget, and which budgets leaked                     |
| Budget AI Report   | AI summaries of budget performance, generated by the Budget Performance AI Summary workflow |

### Manage Budgets

<\<SS = budgets-manage-list>>

| Column                      | What it shows                                                             |
| --------------------------- | ------------------------------------------------------------------------- |
| Budget Name                 | The name you gave the budget                                              |
| Report Name                 | The Report the budget is built on                                         |
| Status                      | **Published** or **Draft**                                                |
| Budget Type                 | **Auto** if OneLens suggested the amounts, **Manual** if you entered them |
| Budget Date                 | The period the budget covers, for example APR 2026 to MAR 2027            |
| Created On, Last Updated On | When the budget was created and last changed                              |

Search by budget name, or use **Filters** to narrow the list.

<\<CONFIRM = what the two row icons do (chart icon, and the options in the menu icon)>>

<\<CONFIRM = how a budget becomes Draft vs Published>>

### Open a budget

Open any budget from the list to see its settings.

<figure><img src="https://3963693991-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FiyNGpqVYfmDF6qt7Lzar%2Fuploads%2FC0EiAs11DFH2mhhUvlhG%2Fimage.png?alt=media&amp;token=8c6ff46b-0563-4bae-8a63-5f9b9d3c3d58" alt=""><figcaption></figcaption></figure>

The **Budget Details** tab shows:

* The **Budget Report** the budget is built on.
* The **Granularity**, for example Monthly.
* The **Start Date** and **End Date**.
* The **Budget Breakdown** table. Each row is one value of the dimension the budget is split by, such as one GCP project. Each column is one period. Use **Export** to download it.

The **Audit Log** tab lists the changes made to the budget.

### What's next

* [Create a Budget](/govern-control-and-governance/budgets/create-budgets.md)
* [Budget Performance](/govern-control-and-governance/budgets/budget-performance.md)
* [Budget Alerts](/govern-control-and-governance/budgets/budget-alerts.md)


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.onelens.cloud/govern-control-and-governance/budgets.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.
