> For the complete documentation index, see [llms.txt](https://docs.peakcommerce.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.peakcommerce.com/product/settings/billing-catalog/plan-entitlements.md). # Plan Entitlements **Settings → Billing & Catalog → Plan Entitlements** is where you say what each plan actually grants — turning the capabilities you defined in [**Feature vocabulary**](/product/settings/billing-catalog/plan-entitlement-features.md) 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. --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter: ``` GET https://docs.peakcommerce.com/product/settings/billing-catalog/plan-entitlements.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.