> For the complete documentation index, see [llms.txt](https://docs.platform9.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.platform9.com/managed-openstack/user-administration/user-admin-customize-user-quota.md).

# Customize User Quota

You can customize the quota related to cores, RAM and number of allowed instances for a user.

When the user-level quota is enabled, the values specified for the user-level quota override the default values specified at the tenant level for the user. You can specify the custom values for one or more quota fields.

If you do not specify the value for a quota field, that is, you leave a quota field blank, the tenant-level quota is applied to such a field.

You must be an administrator to perform this operation.

To customize user quota, follow the steps given below.

1\. Log in to Clarity.

2\. Click Tenants and Users in the left panel.

3\. Click the Users tab.

4\. Select the checkbox for the user whose user quota you want to customize.

<figure><img src="https://1553994354-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FzFKnLSEoXJl99ahgFggb%2Fuploads%2Fgit-blob-9af0f0566d50c6e47d23f50271f477346a300ee5%2F1605283220.png?alt=media" alt=""><figcaption></figcaption></figure>

5\. Enter the quotas in one or more fields, along with the unit of measurement where it is required.

6\. Click Save.

The changes to the user-level quota are saved for the user.

The specified quotas are applicable to the user when the user logs in to and uses Platform9 Managed OpenStack.


---

# 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.platform9.com/managed-openstack/user-administration/user-admin-customize-user-quota.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.