> For the complete documentation index, see [llms.txt](https://docs.tebex.io/creators/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.tebex.io/creators/growth-and-success/fivem-beta-assets-best-practices.md).
# FiveM Beta Assets Best practices
***
A FiveM script creator may want to create a “Beta” asset—a temporary asset given to a buyer to test, review, or use. Cfx and Tebex policies don’t allow assets to be revoked, so the asset given to the buyer is final and stays with the buyer.
Below are Creator Success' best practices when it comes to Beta Assets:
### Assets are final and non-revocable
When giving an asset to a buyer, they will keep it indefinitely. **There is no way for the seller, Tebex, or Cfx to revoke it.**
### Trust
Only grant beta assets to a buyer you fully trust. If you are worried about the asset being leaked, re-sold, shared, etc. - **do so at your own risk.**
### Hidden packages
When creating these beta assets, keep them hidden in your Tebex store so other buyers won’t be able to buy them. You can still change and grant them, but they won't be visible in your public store.
---
# 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 dynamically by asking a question.
Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:
```
GET https://docs.tebex.io/creators/growth-and-success/fivem-beta-assets-best-practices.md?ask=&goal=
```
`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.
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.