> 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/e-signature-confirmation.md).
# E-Signature Confirmation
Here is how you can have your users confirm asset checkout with their signature.
## Setting up for e-signature
1. Go into your dashboard settings using the cog next to Asset Management.
2. Toggle both EULA and e-signature features on.
3. Follow [EULA set up instructions](/asset-management/eula-checkout-confirmation-page.md) for your asset confirmation.
4. Start [checking out assets](/asset-management/assets/checking-assets-out-and-in.md) to users.
## Users View with Confirmation
1. Your users will get a confirmation email after assets are checked out under "Pending Checkout". This email will take 10-15 minutes to send in order to compile all assets being checked out to that user into a single email.
2. The user will click the open link and will be brought to their confirmation page. 
3. They will then need to sign using the box at the bottom of the page before confirming the checkout.
4. Once the checkout is confirmed, they get a confirmation prompt and can close out the window.
## After User Confirms
You can then view all signatures for that asset by going to "Assets" searching the asset and clicking the view more arrow. Click on EULA History for current and past checkouts.
---
# 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/e-signature-confirmation.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.
