> 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/troubleshooting/escrow-licensing.md).

# Entitlement or protected-file error

Separate entitlement issues from protected-file and transfer problems.

## “You lack the required entitlement”

**Meaning:** The server is not authorized to use the protected asset. Cfx.re documents this message as the result of an unauthorized server attempting to run a resource.

### Checks and fixes

1. Sign in to the [Cfx.re Portal](https://portal.cfx.re/) using the account used for the purchase and check that the asset is assigned to it.
2. Compare the purchase account with the owner of the server license key actually in use. Check in your private server administration or hosting panel.
3. Check whether your host manages the key through its panel and overrides the configuration file.
4. For a subscription product, verify that its entitlement is active. Not every product is a subscription.
5. After correcting the key/account assignment, perform a planned server restart and test again.

{% hint style="danger" %}
Never post your full server license key. Remove it from logs and screenshots. Support needs the error and account-assignment information, not the secret key.
{% endhint %}

## “Failed to verify protected resource”

**Possible causes:** Incomplete, damaged, or modified protected files.

1. Download the product again through the intended delivery method.
2. Extract and upload the complete package. Make sure your upload tool includes any supplied hidden files.
3. Use the untouched package and a server version matching the product requirements.
4. If it still fails, save the startup log and contact support.

## Unusual syntax errors in protected files

An error such as `syntax error near '<\1>'` in a protected file can indicate that the file is not being processed correctly. Check entitlement, supported server environment, and upload integrity. An ordinary syntax error in a configuration file you edited is a different issue.

Do not edit or decrypt protected files. Test a fresh download with the required server version.

## Paid, but entitlement is missing?

Check your purchase confirmation, account, and product name. Send the order reference privately to StudioWorks support. Do not purchase the same product again before the account assignment is checked.

Technical reference: [Cfx.re Asset Escrow](https://docs.fivem.net/docs/server-manual/asset-escrow/).

***

[StudioWorks Store](https://tebex.studio-works.net/) · [Discord & Support](https://discord.gg/UmqU67rp4v)


---

# 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/troubleshooting/escrow-licensing.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.