# Set quotas > Set Orchard organization caps and member allowances, read the Usage page, and transfer project ownership. Source: https://docs.orchard.hackclub.com/teams/quotas/ A cluster has a fixed amount of CPU and memory, and every organization on the instance shares it. Quotas stop one person or project from using all of it, so a runaway deploy fails with a clear message instead of starving everyone else. Quotas apply only when [resource limits](/operate/resource-limits/) are on. If a superadmin turns limits off, Orchard does not check caps or allowances, and the **Usage** page shows **Resource limits are off**. ## How limits apply Orchard checks three limits when you create, scale, or resize an app or database: 1. The organization cap, [set by a superadmin](/operate/manage-organizations/#set-resource-quotas). 2. The project cap, if the project has its own. It covers the whole project, including its environments. 3. The member allowance of the project owner. Orchard refuses a request that does not fit, and the message names the limit. Apps that already run keep running, and you can still restart them. Quotas count the CPU and memory that you select for an app. The resource picker shows the remaining budget while you size an app. If an app cannot start because its project is out of room, the app page shows which limit is used up. For example, `This app can't start: its project's memory limit is used up.` To continue, raise the limit, or stop or shrink another app. A member with no allowance of their own uses the organization's default allowance. If the organization has no default, the member has no limit. A cap or allowance must be greater than 0. To remove one, leave it blank. ## Set an organization cap You must be a superadmin. 1. Go to **Instance admin** > **Organizations**. 2. On the organization row, open the **More** menu and select **Resource quotas**. 3. Set any of **CPU** (millicores), **Memory** (MiB), **Max pods**, **Max services**, **Max projects**, **Max environments**, and **Max deployments**. Leave a limit at **Unlimited** to remove it. 4. Select **Save quotas**. Orchard applies the quotas to the cluster when you save. ## Set a member allowance You must be an organization owner or admin. 1. In your organization, go to **Usage** > **Members**. 2. To set the default, select **Edit** in **Default allowance**. 3. To set one person's allowance, select the edit control on their row. ## Read usage Go to **Usage** in your organization. Owners and admins see all of the following tabs. Other members see **Yours**. | Tab | Shows | | ---------------- | ----------------------------------------------------------------------- | | **Organization** | Capacity against caps, and usage by project. | | **Yours** | The workloads that you own. | | **Members** | The default allowance, and each member's usage against their allowance. | | **Right-sizing** | How workloads compare with their allocated resources. | Size apps from [metrics](/run/monitor-an-app/#read-metrics) over a time range instead of a single reading, so that the size covers the peak. ## Transfer project ownership Every project has an owner, who is the person who created it unless ownership has moved. All apps and databases in the project count against the owner's allowance. The project owner, or an organization owner or admin, can start a transfer. The new owner must already be a member of the project. To start a transfer from the dashboard: 1. Go to the project **Settings** tab. 2. In **Danger zone**, select **Transfer** next to **Transfer ownership**. 3. In **New owner**, select the person. 4. Select **Send request**. To start a transfer from the CLI: ```bash orchard project transfer request someone@example.com ``` The recipient accepts or declines the request. The request expires after seven days. To list and accept requests from the CLI, run the following commands: ```bash orchard project transfer list orchard project transfer accept ``` Orchard rejects the transfer if the project does not fit in the new owner's allowance. To continue, raise the allowance or reduce the project. When the recipient accepts, they become a project admin. The previous owner keeps their current project role. ## Related resources - [Scale an app and set resources](/deploy/scaling/) - Choose the CPU and memory that count against a quota. - [Review usage](/teams/usage/) - Read where an organization's capacity goes. - [Manage nodes and pools](/operate/nodes/) - Add capacity to the cluster itself.