---
title: "Managing tenant caps"
description: "If you have multiple tenants under your account, Coassemble applies a per-tenant cap on AI feature usage. This article explains why the cap exists, what the defaults are, and how to manage it."
canonical_url: "https://support.coassemble.com/articles/managing-tenant-caps-7jY5bS2rJA"
md_url: "https://support.coassemble.com/articles/managing-tenant-caps-7jY5bS2rJA.md"
---
# Managing tenant caps

If you have multiple tenants under your account, Coassemble applies a per-tenant cap on AI feature usage. This article explains why the cap exists, what the defaults are, and how to manage it.

## Why tenant caps exist

Tenants under an Embed customer share the customer's total monthly allowance for narration tokens and AI image generation events. To prevent any single tenant from consuming the whole pool, Coassemble applies a hard cap at the tenant level for AI metrics.

When a tenant hits its cap, AI feature usage is blocked at the tenant level until you raise the cap or it resets at the start of the next calendar month. The block applies to that tenant only. Other tenants and the parent customer keep working.

## Default tenant caps

Every new tenant starts with Hub-equivalent caps:

* 250,000 narration tokens per month
* 150 AI image generation events per month

These defaults apply even if your customer-level allowance is set to unlimited.

## How tenant caps interact with customer-level allowance

The two enforcement layers run independently:

* **Customer-level caps on AI features for Embed plans are soft.** If your account goes over its overall allowance, generation keeps working and the breach is surfaced to your account manager.
* **Tenant-level caps are hard.** A tenant that hits its monthly cap is blocked from generating AI content until the cap is raised or the month rolls over.

Hitting one cap doesn't affect the other.

## Setting and changing tenant caps

You can change a tenant's cap via the Coassemble API:

* Set a different numeric cap.
* Set the cap to "unlimited" if you want a specific tenant to draw freely from your customer-level allowance.

For the API endpoint and request shape, see the [developer documentation](https://developers.coassemble.com).

## What tenant caps don't cover

* **IR and AR don't have tenant-level caps at launch.** Recipient counts are enforced at the customer level only.
* **Top-ups don't apply at the tenant level.** If a tenant is running low mid-month, raise its cap (or set it to unlimited) rather than topping up.
* **Tenants can't change their own caps.** Only the parent customer can, via API.

## Seeing per-tenant usage

The Per-Tenant Usage Reporting API exposes consumption breakdowns by tenant for any time window, so you can build dashboards or alerts on top of the data. See the developer documentation for the endpoint shape.

## Common questions

### Can I bulk-set caps for all my tenants at once?

There's no bulk-set helper at launch. You can call the API for each tenant.

### What happens when a tenant cap is reached?

AI generation pauses for that tenant. Other tenants keep working. The tenant resumes at the start of the next calendar month, or as soon as you raise the cap.

### Are tenant caps visible to the tenant's admin?

Not at launch. Cap visibility is at the parent customer level via the API.