> For the complete documentation index, see [llms.txt](https://docs.itsaffinity.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.itsaffinity.com/product-guides/lms-authoring/use-cases/policy-attestation-example.md).
# Policy Attestation Example
You can design a policy attestation in the editor in a similar method to the above image. You will:
1. Upload the policy you need the learners attest to having read.
2. Add a multiple choice question with the appropriate answers, such as "Yes" or "No". Optionally you can template their name into the question.
3. Publish and assign this training as needed.
To the learner, this ends up looking like the following:
And, after they have answered successfully:
In your admin dashboard they will then be marked as completed only if they select the right choice.
You can also view the individual question response data from your admin dashboard as well.
---
# 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.itsaffinity.com/product-guides/lms-authoring/use-cases/policy-attestation-example.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.