> For the complete documentation index, see [llms.txt](https://docs.esignet.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.esignet.io/home/esignet-2.0.0/local-deployment/try-it-out/end-user-guide.md).
# End User Guides
Fast, secure authentication for residents made easy.
The guides in this section walk through what logging in with eSignet actually looks like from an end user's point of view — step by step, through a real relying-party application, rather than as an abstract flow diagram. Each guide sets the same underlying eSignet login and consent experience in a different real-world context, so you can see how the authentication factors and consent flow described under [Features](/home/esignet-2.0.0/readme/features.md) come together in practice, whichever kind of service is asking a resident to prove who they are.
> **Before you start**: these guides assume some familiarity with how eSignet handles identity claims — see [Claims Configuration](/home/esignet-2.0.0/develop/configuration.md#claims-what-personal-data-a-client-can-receive) under Developer Guide if you haven't already. Screenshots and specific steps shown in each guide are for demonstration purposes only, and may differ from what you see in your own environment.
### Guides in This Section
---
# 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.esignet.io/home/esignet-2.0.0/local-deployment/try-it-out/end-user-guide.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.
