For the complete documentation index, see llms.txt. This page is also available as Markdown.

Plan Entitlements

Settings → Billing & Catalog → Plan Entitlements is where you say what each plan actually grants — turning the capabilities you defined in Feature vocabulary into concrete, per-plan entitlements your application reads at runtime.

The grid

The page lists your plans and the features each one grants. For any plan/feature pairing a feature is either Included (granted on this plan), Not included, or shown as Included in this plan on the plan's own view. Filter with All plans or the Search plan or feature… box to find a pairing quickly. If nothing grants a feature yet, it reads No plan grants this today.

Granting a feature to a plan

Add an entitlement to a plan to grant a feature. Beyond the on/off decision, an entitlement can carry:

  • Value (JSON) — the value your app receives for the feature (for example a numeric seat limit, a tier string, or a structured object). This is how one feature expresses different limits on different plans.

  • Unlimited — switch this on instead of a value when the plan grants the feature with no cap (Or switch on Unlimited).

Each entitlement is delivered to your app under the feature's Sent to your app as key, so your code gates on the key, not on the plan name — change which plan includes a feature and your app follows automatically.

Removing

Removing an entitlement (Entitlement removed from plan) revokes that feature from the plan. Accounts on that plan stop receiving it under its key on their next resolve. Start from No entitlements yet. Add one to say what a plan grants. when a plan has none.

Last updated

Was this helpful?