> ## Documentation Index > Fetch the complete documentation index at: https://controlplanecorporation-majid-docs-content-expansion.mintlify.site/llms.txt > Use this file to discover all available pages before exploring further. # Quota > One cap per resource in every org, counted per GVC for workloads, identities, and volume sets. The allowed max decides whether the next create succeeds, and only an approved increase request moves it. A quota is a limit on how much of one resource your [org](/concepts/org) may use: a pair of numbers, `current` for what the org uses right now and `max` for the most it is allowed to reach. When `current` reaches `max`, creating more of that resource is rejected until usage drops or the max is raised. ## How It Fits | Relationship | Rule | | ------------ | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | Org | Every quota belongs to one org, and each org draws on its own allowance: usage in one org never counts against another. | | GVCs | Most quotas count the whole org ([domains](/reference/domain), [secrets](/reference/secret), [agents](/reference/agent), the number of [GVCs](/concepts/gvc)). [Workloads](/concepts/workload), [identities](/concepts/identity), and [volume sets](/reference/volumeset) are counted separately in each GVC. | | Workloads | A few quotas cap size rather than count: CPU and memory per workload, and how high its `maxScale` may go. | | The catalog | The read-only list of every quota that can exist: its name, unit, description, and default max. It is the same for every org; your org's own quota list carries the live `current` and `max` for the quotas the org has drawn on. | | Policies | Reading quotas and submitting increase requests takes the org-level `view` [permission](/reference/quota#permissions), which the built-in org [policy](/concepts/access-control) grants every member. | The same quota, workloads-per-gvc, at two moments. When the quota is reached, current usage is 20 and the allowed max is 20. After an approved increase, current usage is still 20 and the allowed max is 50. When usage reaches the max, creating more of that resource is rejected, and one approved increase request raises the max. One quota, one approved request, and room for 30 more workloads. A [quota increase request](/guides/manage-quotas) moves through one of three statuses. | Status | Meaning | | ---------- | ------------------------------------------------------------------------------------------------------------- | | `pending` | The request has been received and is awaiting review. | | `approved` | The request was granted, and the new max is applied to your org. | | `denied` | The request was reviewed and not granted; the max is unchanged, and Control Plane shares the reason with you. | ## Key Behaviors * **A request asks for one quota's new max.** You submit the exact quota name, taken from your org's quota list or the catalog, and the max you want. Requests within the range Control Plane grants automatically are approved immediately; larger ones wait as `pending` for review by the Control Plane team. * **You can track a request after submitting it.** Retrieve it by its ID or [list your org's requests](/guides/manage-quotas#check-the-status-of-a-request), optionally filtered by status; each request records the requested max, who submitted it, and who resolved it. * **Control Plane notifies you of the outcome.** The answer goes to whoever submitted the request, and an approved max appears on the quota the next time you view your quotas. * **Deleting a resource frees its quota room at once.** `current` drops in the same operation that deletes the resource, so clearing out what the org no longer needs is the immediate alternative to raising a max. * **A quota near its limit is visible in metrics.** Once a quota passes half its max, your org's [built-in metrics](/reference/quota#metrics) report it as `quota_utilization_percent`, so you can chart and alert on a quota before creations start failing. ## Gotchas * **The rejection names the quota.** Creating a resource whose quota is full fails with `Quota has been maxed out (max=20). You can request quota increase from Control Plane administrators.`, so the error itself tells you which quota to raise. * **An increase request never lowers a quota.** A request for a value at or below the current max is treated as already satisfied and changes nothing. To lower a max, contact [support@controlplane.com](mailto:support@controlplane.com). * **A quota cannot be edited directly.** It is a built-in object that Control Plane maintains, and an edit is refused whatever your permissions; raising a max goes through an increase request. * **The catalog carries no numbers for your org.** A catalog entry describes a quota in general, its default max included; the live `current` and `max` are on your org's own quota list. * **The cap on orgs themselves lives outside the org.** How many orgs you may create is a [billing account](/concepts/billing) limit raised through support, separate from the quotas an org holds. ## Learn More The resources that carry a quota, the utilization metric, and permissions. View your quotas, browse the catalog, and submit and track increase requests through the API. The environment whose allowance every quota caps, and what else it holds. What pays for your orgs, with a limit of its own on how many you create.