> For the complete documentation index, see [llms.txt](https://docs.devolutions.net/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.devolutions.net/rdm/da/concepts/intermediate-concepts/documentation.md).

# Dokumentation

Opret dokumentationssider i programmet i Remote Desktop Manager for at gemme procedurer, runbooks og fejlfindingsnoter med arbejdsområdets tilladelser.

Dokumentation i programmet lader Dem oprette sider med formateret tekst eller Markdown, der gemmes i avancerede arbejdsområder, så De hurtigt kan slå dem op i konteksten. Brug den til at registrere procedurer, runbooks, tjeklister og fejlfindingsnoter dér, hvor Deres team arbejder i Remote Desktop Manager.

Dokumentationssider kan sikres som alle andre elementer og nyder godt af arbejdsområdets tilladelser og mulighed for revision. Integrer links, kodestykker og billeder, og organisér indholdet efter mappe eller boks, så konteksten er tydelig. Det holder viden ajour, mindsker skift af kontekst og hjælper nye teammedlemmer med at følge standardiserede trin med tillid.

#### Relaterede emner

* [Dokumentation](/rdm/da/user-interface/content-area/dashboard/dashboard-tabs/documentation.md)


---

# 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.devolutions.net/rdm/da/concepts/intermediate-concepts/documentation.md?ask=<question>&goal=<user_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.