> For the complete documentation index, see [llms.txt](https://docs.fortifiedid.se/use-cases/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.fortifiedid.se/use-cases/hands-on-use-cases.md).

# Hands-on use cases

This section contains **hands-on use cases** and technical examples for multiple Fortified ID products. The pages here are intended for readers who want practical guidance, configuration examples, and step-by-step help for implementing a specific scenario.

If you are instead looking for **business-oriented use cases** that are easier to relate to at a high level, those are available in the relevant product documentation. These pages describe common needs, scenarios, and outcomes without going into detailed configuration.

Examples:

* [Fortified ID Access - Common Use Cases](https://docs.fortifiedid.se/access/next-access/common-use-cases)
* [Fortified ID Control - Common Use Cases](https://docs.fortifiedid.se/control/next-control/common-use-cases)

Use this section when you want to understand **how to configure** a scenario. Use the product documentation when you want to understand **what the product can be used for** in practice.


---

# 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.fortifiedid.se/use-cases/hands-on-use-cases.md?ask=<question>&goal=<endgoal>
```

`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.