Example
A company manages multiple workspaces. Each workspace can be on a different tier — Workspace A is on the Free tier (100 requests/month), while Workspace B is on the Pro tier (10,000 requests/month). Both are billed to the parent organization.
When to use sub-entity plans
Use sub-entity plans when entities under a customer need different plan tiers. If all entities get the same features and limits, use sub-entity balances instead.| Scenario | Approach |
|---|---|
| All seats get the same 50 credits/month | Sub-entity balances |
| Each seat can be Free or Pro tier | Sub-entity plans |
Setting up
- CLI
- Dashboard
Create your plans as normal — no special entity configuration needed on the plan itself. The entity-level attachment happens at runtime via the API.Push changes with
autumn.config.ts
atmn push.Attaching plans to entities
First, create the entity. Then attach a plan to it by passing theentity_id in the attach call:
Create the entity
Attach a plan to the entity
Checking and tracking per entity
Pass theentity_id to scope check and track calls to a specific entity:
Upgrading an entity’s plan
To upgrade or downgrade an entity, attach the new plan with the sameentity_id. The same upgrade/downgrade logic applies:
Cancelling an entity’s plan
Usebilling.update with cancelAction to cancel an entity’s plan. The same cancel/uncancel behavior applies.

