Workspace limits let an agency decide how much a client workspace can use. For example, you can let a restaurant's Admin connect up to 20 publishing destinations and request up to 100 AI images each month. The client can work within those limits without gaining control of your agency's billing or other workspaces.
Set a limit
Open Settings > Workspace settings > Usage limits in the client's workspace. Only the account Owner can save changes. Admins and other members can inspect the limits, but cannot raise them through a custom role, API key, or AI assistant.
All fields start with no additional workspace limit. Enter a whole number to add a cap, leave a field blank to remove it, or enter zero to prevent new consumption. Review the usage shown beside each field, then choose Save limits.
Choose Apply to all workspaces to replace these settings in all workspaces owned by the account. The confirmation explains that blank fields remove previous caps. This applies to existing workspaces; review newly created workspaces separately. If the connection fails during a large update, review the saved settings before retrying.
What each limit measures
| Limit | What it counts |
|---|---|
| Publishing channels | Current connected publishing destinations under the account's channel-counting rules |
| CRM channels | Current CRM channel selections in this workspace |
| Email audience | Contacts saved in this workspace's Email audience |
| Media storage | Stored media bytes, including capacity reserved for pending uploads |
| Team members and invitations | Members and pending invitation seats |
| AI text | Generation requests during the UTC calendar month |
| AI images | Requested images during the UTC calendar month |
| AI video | Requested video seconds during the UTC calendar month |
| Email sending | Recipient sends during the UTC calendar month |
| Publishing volume | Destination publishing reservations during the UTC calendar month |
| Publishing automation | Publishing automation occurrences during the UTC calendar month |
Monthly counters reset on the first day of each month at 00
UTC. AI caps apply to managed AI access and your own provider key. Usage includes reserved work, so it is not a report of successfully delivered posts or emails. Uncertain provider outcomes keep their reservations to prevent an accidental duplicate request.Shared capacity still applies
A workspace cap does not reserve channels or purchase an add-on. If the account has 100 channels, giving six clients a cap of 20 does not create 120 channels. The account's remaining capacity must also allow a new connection.
Publishing, CRM, Email, AI, and provider allowances retain their own rules. A limit cannot enable a feature that the account cannot access. Advertising spending controls are not included.
What happens when a limit is reached?
The affected action stops and explains which workspace limit was reached. The account Owner can adjust the cap, or the team can free current capacity where appropriate. A monthly cap becomes available again after its UTC reset.
Lowering a cap does not delete content or disconnect existing channels. If a workspace already has 12 channels and the Owner sets its cap to 10, existing connections remain; new connections cannot be added until the workspace is within the cap. This is separate from the channel selection and disconnection review when changing a paid subscription.
CRM access in the same settings area
Open Workspace settings > CRM access to manage the existing workspace and organization CRM access controls. Use Usage limits for a numeric CRM channel cap. Allowing CRM does not select channels or purchase CRM capacity. The CRM settings link opens the central workspace settings area.
API and MCP
Read GET /v1/workspaces/{workspaceId}/usage-limits or call postly.get_workspace_usage_limits to inspect limits and usage. An Owner-authorized integration can replace the policy with PUT to the same route or postly.update_workspace_usage_limits, using the complete limits map and confirm: true after approval.
An omitted or null API field removes that cap. For example, {"channels":20,"ai_images":100} keeps only those two caps. Read the current policy before replacing it so you do not accidentally remove another restriction. Workspace scopes still apply. An Owner-set limit rejection returns HTTP 429 with an explanation; ask the Owner to review it instead of retrying repeatedly or buying capacity automatically.