> For the complete documentation index, see [llms.txt](https://docs.finops.softwareone.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.finops.softwareone.com/policies/quotas-and-budgets/manage-quota-or-budget.md).
# Manage quota or budget
When a quota or budget policy has been created, Organization Managers can edit the policy name or delete the policy.
When editing a policy, you cannot change the policy type or update properties, including filters associated with the quota or budget.
### Rename a quota or budget
To rename an existing quota or budget policy:
1. Navigate to the **Quotas and budgets** page.
2. In the list of policies, find the policy you want to manage, then select the policy name.
3. On the policy details page, select the edit icon 
.
4. Under **Name**, enter the new name, then save your changes.
### Delete a quota or budget
{% hint style="warning" %}
Deleted policies cannot be restored.
{% endhint %}
To delete an existing quota or budget policy:
1. Navigate to the **Quotas and budgets** page.
2. In the list of policies, find the policy you want to manage, then select the policy name.
3. On the policy details page, select **Delete**.
4. In the confirmation panel, select **Delete** to confirm the action.
---
# 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.finops.softwareone.com/policies/quotas-and-budgets/manage-quota-or-budget.md?ask=&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.