> 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/entitlement-groups-bundles.md).
# Entitlement Groups (Bundles)
Group multiple entitlements under a single Entitlement Group to sell bundles, add seats later, or manage combined hardware-and-software licenses with one access code.
Each time you create a new entitlement, Zentitle2 will also create an "entitlement group" by default; you need to create entitlements and then if you add further entitlements to the original one it becomes a "group" by default - and that group can now be addressed via its unique ID - ideal for using in your billing and accounting systems.
This group is irrelevant for single entitlements, but it becomes useful when you wish to group offerings—the classic example being "bundles" of products sold together. Also, a group is ready for future use, so you can build a group later, as your business model requires, by adding entitlements together after shipping to a client.
**The key benefit of a group is flexibility when packaging your software—you can now combine different entitlements into a single billable entity. Also, the end user can access a single account or license code for a group of functionalities across your products and offerings.**
The Entitlement Groups feature introduces a new way to manage licensing for complex customer orders by allowing multiple entitlements to be grouped under a single logical entity and, from a business perspective, under a single order. This enables customers to purchase and activate several product configurations as part of a single transaction, improving flexibility and aligning with real-world use cases (e.g., orders with multiple configurable products).
### Business Cases
1. Selling a "bundle" offer. An example is MS Office, which consists of Word, Excel, and PowerPoint products. You can buy them separately and as a "bundle package". In this bundle scenario, you get a better price and only one activation code (or ABL credentials) instead of three separate ones.
2. When customers want to buy extra seats later, after the creation of an entitlement, e.g., they need extra seats for Christmas. You add another entitlement to the Entitlement Group with a subscription plan of 1 month and those additional seats. Zentitle2 will check which entitlement still has seats available and activate the ActivationCode/ABL towards that entitlement. No additional steps or development by the vendor are needed.
3. Selling hardware and software together, and having it all under one activation code or ABL login.
The key here is **one access point** (Activation Code or ABL) to all entitlements in the Entitlement Group.
There is no need to manage separate access for each entitlement. This works both ways: one Activation Code/ABL gives you access to all entitlements in the group, and one Access Code/ABL has to be removed to revoke access to all entitlements in the group.
---
# 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/entitlement-groups-bundles.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.