Per-Client Resource Quota Allocation
Who this is for
Agency account owners or staff with client:manage permission who want to set limits on how many resources each client organisation can provision.
What you will complete
You will configure per-client resource quotas, understand which quota keys are available, and verify that limits are enforced.
What are quotas?
Quotas are hard limits on specific resource types within a client organisation. When a client org reaches a quota limit, provisioning of that resource type is blocked until the quota is raised or resources are removed.
Quotas protect you from a single client unexpectedly consuming your full agency plan's resource allocation.
Available quota keys
| Quota key | What it limits |
|---|---|
servers | Maximum number of active servers |
sites | Maximum number of deployed sites |
apps | Maximum number of deployed apps |
cloud_accounts | Maximum number of connected cloud provider accounts |
team_members | Maximum number of users in the client org |
backups_gb | Maximum backup storage in gigabytes |
ai_actions_per_day | Maximum AI Pilot agent actions per 24-hour period |
Set quotas for a client
Step 1 — Open Agency → Clients and click the client you want to configure.
Step 2 — Click the Quotas tab in the client detail panel.
Step 3 — The current quota values are shown. A value of Unlimited means no cap is enforced.
Step 4 — Click Edit quotas.
Step 5 — Enter numeric limits for each quota key you want to restrict. Leave a field blank or set to 0 to keep it unlimited.
Step 6 — Click Save quotas.
Changes take effect immediately. If the client already has more resources than the new quota allows, existing resources are not deleted — but new provisioning is blocked until usage drops below the quota.
View quota usage
On the client's Quotas tab, each row shows:
- Current limit
- Current usage
- Usage bar (green = under 80%, amber = 80–99%, red = at limit)
Agency staff can view quota usage for all clients from Agency → Overview where a "Quota alerts" section surfaces any clients at or near their limits.
Common errors
Client can still provision resources after quota is set Cause: Quota changes may take up to 60 seconds to propagate. Fix: Wait 60 seconds and try again. If provisioning still succeeds, verify the quota was saved correctly by returning to the Quotas tab.
"Quota exceeded" error appears for a client Cause: The client has reached a hard limit you set. Fix: Either increase the quota or ask the client to remove unused resources.
Quota tab is not visible Cause: Your agency role does not include client:manage. Fix: Ask the agency owner to update your role permissions.