> 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/private-cloud-director/identity-and-multi-tenancy/tenant-quotas-user-quotas-and-vm-leases.md).
# Tenant Quotas, User Quotas and VM Leases
space.vars.product\_name enables you to apply limits or quotas for various resources at each tenant and user level, to ensure that no single tenant can use more than their entitled amount of resources. In addition, you can configure VM lease policy to control how long a virtual machine may exist.
{% hint style="info" %}
Note: User level quotas can be used for controlling individual users limits. User level quotas override tenant quotas for the respective users.
{% endhint %}
{% hint style="warning" %}
You must be an administrator to edit, create, and delete quotas and leases.
{% endhint %}
### Virtual Machine Lease Settings
A virtual machine lease controls how long a single virtual machine created by a user in a given tenant may exist, measured in days. Setting a virtual machine lease will cause any virtual machine created under the defined tenant to be **automatically deleted once the lease age is met.**
### Tenant Quotas
Following table describes all tenant level quatas supported.
| Field | Description |
| -------------------------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------- |
| **Compute Quotas** | |
| Core | Total number of cores to be available to the tenant. This is the maximum number of cores available collectively to the users belonging to the tenant. |
| RAM | Total RAM to be available to the tenant. Select the unit of measurement for the RAM, after the numeral value. |
| VMs | Total number of virtual machine instances that can be created on the tenant. |
| Server Groups and Server Group Members | Total server groups that this tenant can create and maximum number of server group members that each server group may have. |
| **Block Storage Quotas** | |
| Block Storage | Total block or persistent storage space to the tenant. Select the unit of measurement for block storage, after the numeral value. |
| Volumes | Total number of volumes available to the tenant. |
| Volume Snapshots | Total number of volume snapshots available to the tenant. |
| Max Volume Size | Maximum size of volume in the tenant. |
| **Network Quotas** | |
| Networks | Total number of networks available to the tenant. |
| Subnets | Total number of subnets across all networks available to the tenant. |
| Routers | Total number of routers available to the tenant. |
| Ports | Total number of ports available to the tenant. |
| Floating IPs | Total number of floating IPs available to the tenant. |
| Security Groups | Total number of security groups available to the tenant. |
| Security Group Rules | Total number of security group rules available across all security groups on the tenant. |
### User Quotas
A user quota sets compute limits (Cores, RAM, and Instances) for an individual user within a specific tenant. A user quota overrides the tenant's compute quota for that user only; it does not affect other users in the tenant, and it does not cover block storage or network quotas, which are set only at the tenant level.
A user quota can be applied only to a user whose role in the selected tenant is not **ReadOnly**. A user quota cannot be applied at all to a user who holds a system-level role (**Platform Admin**, **Service Provider Domain Admin**) or a domain-level role (**Customer Domain Admin**), regardless of that user's role in the selected tenant. See [RBAC Roles and Permissions](/private-cloud-director/identity-and-multi-tenancy/rbac-roles-and-permissions.md) and [Granular RBAC Roles (Beta)](/private-cloud-director/identity-and-multi-tenancy/rbac-roles-and-permissions/granular-rbac-roles.md) for role definitions.
To manage a user's quotas:
1. Navigate to **Settings** > **Tenants & Users** > **Users**.
2. Select the user in the grid view, then choose **Manage Quotas** from the Actions menu.
3. In the **Edit Quotas for User** dialog, select the **Tenant** to set quotas for.
4. Set the **Cores**, **RAM**, and **Instances** limits, then select **Update User Quotas**.
If the selected user's role does not allow a user quota, the dialog shows a warning explaining why and disables the quota fields.
## Related Pages
* [RBAC Roles and Permissions](/private-cloud-director/identity-and-multi-tenancy/rbac-roles-and-permissions.md): the built-in Admin, Self-Service User, and ReadOnly roles.
* [Granular RBAC Roles (Beta)](/private-cloud-director/identity-and-multi-tenancy/rbac-roles-and-permissions/granular-rbac-roles.md): the system-level and domain-level role definitions.
---
# 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://docs.platform9.com/private-cloud-director/identity-and-multi-tenancy/tenant-quotas-user-quotas-and-vm-leases.md?ask=&goal=
```
`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.