> For the complete documentation index, see [llms.txt](https://docs.nalpeiron.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.nalpeiron.com/zentitle2-docs/ui-entitlements/entitlements.md). # Entitlements Learn how Zentitle2 entitlements track what each customer has purchased and let you dynamically upgrade, downgrade, or change their rights without new license files. ## About Entitlements Entitlements track what your customers have purchased and all changes through the lifecycle. In the context of software licensing, entitlement refers to the specific rights and permissions that a customer has to use a particular software product. An entitlement is essentially a record of what a customer has purchased, determining what they can do with the software. Entitlements can include a wide range of permissions and restrictions, depending on the specific licensing agreement. Some common examples of entitlements include: * The number of users or devices that are allowed to access the software * The specific features or modules that are included in the license * The duration of the license, including start and end dates * The level of technical support that is included with the license * Any restrictions on how the software can be used or distributed Entitlement management is an important part of software licensing, as it helps ensure customers use the software in compliance with the licensing agreement. By tracking entitlements, software vendors can ensure customers use the software within the limits of their licenses, helping prevent misuse and piracy. ### **Easily Control Entitlements** Using our Dynamic Entitlements, the complexity of license entitlement updates is completely removed for you and your customers.\ \ You can easily upgrade, downgrade, or change features on demand, without the end-user having to do anything to use what they now own.\ \ Legacy licensing platforms often force your customers to install a new license when they want to upgrade or modify their rights, unnecessarily overwhelming them with complex license file management. Not with Zentitle. Zentitle enables you to provision your customers (B2B, B2C, B2B2C) and manage their rights with simple license activation and deactivation. **Any environment** Easily deploy on-premises, in networks, to SaaS, or with embedded devices and IoT **Any business model** Subscription, Concurrent, Consumption, Feature-Based models, and more **Account-based licensing** Log in and use for your customers, with username and password **Frictionless for end-users** Licensing tasks are so simple, support tickets drop by up to 60% ### **Track Entitlements** Maximize revenue opportunities by understanding exactly how your customers use the plans and licenses they’ve purchased. This will allow you to target and grow accounts with the greatest sales potential.\ \ With these insights, you can reduce churn, maximize renewal rates, and identify accounts ripe for cross-sell and upsell opportunities. **Improve development** Once you know how your customers use your software, you can make informed decisions when developing your product.\ \ By knowing what users use and what they don’t, avoid wasting effort on low-value features and focus on delivering functionality that will delight existing customers and attract new ones. ## How Entitlements Work When a customer purchases a license, you can generate an entitlement (either manually or automatically) from the appropriate offering for that customer. {% hint style="info" %} Individual attributes of that entitlement can then be overridden over its lifetime as appropriate (e.g., upgrading from one edition to another, renewing the subscription term, etc.). {% endhint %} An **entitlement group** is created for each entitlement. --- # 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 by asking a question. Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters: ``` GET https://docs.nalpeiron.com/zentitle2-docs/ui-entitlements/entitlements.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case. 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.