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

Feature Vocabulary

Settings → Billing & Catalog → Feature vocabulary is where you define the named capabilities and limits your application gates on — before you grant any of them to a plan. A feature here is a stable key your app checks at runtime ("does this account get advanced reporting?", "how many seats?"), independent of which plans currently include it.

Adding a feature

Use New feature to add one. Each feature is the vocabulary term your app reads — give it a clear name and the key it is sent to your app as, because that key is the contract: your code looks it up by that exact key, so it should not change once your app depends on it.

Features start life unused — No features yet. Add one to start gating your app on it. — and stay that way until a plan grants them on the Plan Entitlements screen.

How it relates to plan entitlements

Feature vocabulary is the definition layer; Plan Entitlements is the grant layer:

  • Define a feature once here (name + key + shape of its value).

  • Then, per plan, decide whether that feature is included and with what value on the Plan Entitlements grid.

Keeping the vocabulary separate means the same feature can be granted differently across plans (off on one, a numeric limit on another, unlimited on a third) without redefining what the feature is.

Last updated

Was this helpful?