> For the complete documentation index, see [llms.txt](https://studioworks.gitbook.io/studioworks-docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://studioworks.gitbook.io/studioworks-docs/scripts/entitlement-error.md).

# You lack the required entitlement

The console says “You lack the required entitlement to use …” and the protected asset does not start.

{% hint style="info" icon="bolt" %}
**Quick check:** Check the product is assigned to the Cfx.re account used for the purchase.
{% endhint %}

## Fix it

1. Compare that account with the owner of the server license key actually used by your host.
2. Check whether the hosting panel overrides the key in the configuration file.
3. After correcting the assignment, perform a planned server restart. Never post the full license key.

## Check the result

The entitlement error is gone and the resource starts. If the account assignment is unclear, send your order reference privately to support.

## Still happening?

[More detailed checks](/studioworks-docs/troubleshooting/escrow-licensing.md) · [Prepare a support ticket](/studioworks-docs/support/preparing-a-ticket.md)

Include the product version, first error, and the steps you tried. Keep secrets out of logs and screenshots.


---

# 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://studioworks.gitbook.io/studioworks-docs/scripts/entitlement-error.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.