> For the complete documentation index, see [llms.txt](https://docs.limio.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.limio.com/product/pricing/how-to-create-and-propagate-entitlements-with-limio.md).

# Entitlements

Subscribers expect immediate access to their purchases upon confirmation. This can be complex with multiple systems involved in order provisioning or fulfillment. Introducing Limio Entitlement! Limio, as a commerce platform, is the first to recognize successful purchases and can provide real-time webhooks to Access and Identity platforms for granting specific features. Entitlements refer to the features or access a customer receives when subscribing to a product. For instance, a basic subscriber might receive an online product, while a gold subscriber gains an online product plus a physical product and online support.

## **Creating and mapping Entitlements**

To create an Entitlement within Limio, click Entitlements on the Catalog side menu. Click on the "+" button, then "Add Entitlements". Make sure to give the Entitlement a name and a label. A code can also be provided to identify the Entitlement within a system external to Limio.

<figure><img src="https://3320508512-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FAw9J8ugfVIqzNtzPQiWO%2Fuploads%2Fgit-blob-f5c1bb24071b5eb7cbddaaf23ad4f3a4a36e6bc1%2Fimage%20(23).png?alt=media" alt=""><figcaption></figcaption></figure>

To associate an Entitlement to a product, click Products on the Catalog side menu. Click on your desired Product, then click on the Entitlements tab. Select your desired Entitlement from the list, and press the Save button in the top right corner.

<figure><img src="https://3320508512-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FAw9J8ugfVIqzNtzPQiWO%2Fuploads%2Fgit-blob-2d64ec35db6aeaab936dfb618110a5c7fc5ecf18%2Fimage%20(24).png?alt=media" alt=""><figcaption></figcaption></figure>

From there, the Entitlement will map to Offers through the Product. Ultimately, Subscriptions will have the Offer. See a full diagram:

<figure><img src="https://3320508512-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FAw9J8ugfVIqzNtzPQiWO%2Fuploads%2Fgit-blob-ce2cc75da2a6b15a010a07a746af8497a112f08a%2Fimage%20(25).png?alt=media" alt=""><figcaption></figcaption></figure>

## **Propagating** **an Entitlement to other systems**

Once the webhook endpoint is setup, Limio will automatically fire entitlements for New Orders, Switch and Cancel/Save. Here is an example of entitlement webhooks sent to Salesforce.

<figure><img src="https://3320508512-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FAw9J8ugfVIqzNtzPQiWO%2Fuploads%2Fgit-blob-970c5ec9847be6c3dc3cff6285904b85067dd574%2Fimage%20(26).png?alt=media" alt=""><figcaption></figcaption></figure>

The payload is described in:

{% content-ref url="<https://docs.limio.com/developers/webhooks/overview>" %}
<https://docs.limio.com/developers/webhooks/overview>
{% endcontent-ref %}

Note that it is possible to send synchronous webhooks (i.e. the order will fail if the webhook is not successfully received by your entitlement system). Learn more at:

{% content-ref url="<https://docs.limio.com/integrations/order-orchestration/callout-plugin>" %}
<https://docs.limio.com/integrations/order-orchestration/callout-plugin>
{% endcontent-ref %}


---

# 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.limio.com/product/pricing/how-to-create-and-propagate-entitlements-with-limio.md?ask=<question>&goal=<user_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.
