> For the complete documentation index, see [llms.txt](https://docs.adminremix.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.adminremix.com/asset-management/eula-checkout-confirmation-page.md).
# EULA Checkout Confirmation Page
Do you have your own EULA that you want your users to agree to during checkout? Toggle this feature on.
After you've toggled this feature on, you will need to enable the Checkout Confirmation within your Categories.
1. Select the [asset category ](/asset-management/settings/categories.md)you want to edit.
2. Click the Confirmation Acceptance and Email User on Checkin/Checkout, then add your own EULA.
3. An email will be sent to the user with a link to confirm checkout.
4. User will see EULA on the confirmation page before accepting.
---
# 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.adminremix.com/asset-management/eula-checkout-confirmation-page.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.
