> 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/knowledge-base/troubleshooting-articles/documentation-tab-is-empty.md).

# Fanen Dokumentation er tom

Løs en tom fane Dokumentation i Remote Desktop Manager ved at kontrollere visningstilladelser og indstillingerne for Internet Explorer Enhanced Security Configuration.

Fanen ***Dokumentation*** i en post er tom, selvom De har valgt ***Nulstil layoutet*** under fanen ***Vindue***.

### Løsning

Kontrollér først, at De har tilladelse til at ***Vise dokumentation*** under ***Administration - Boksindstillinger - Tilladelser - Dokumentation - Vis dokumentation***.

Hvis alt er i orden, kan det skyldes, at serveren har indstillingen IE Enhanced Security Configuration aktiveret. Det kan forhindre og blokere, at dokumentet indlæses. De skal deaktivere den, men vi anbefaler, at De beholder den udvidede beskyttelse.

Se Microsofts [ofte stillede spørgsmål om Internet Explorer Enhanced Security Configuration (ESC)](https://docs.microsoft.com/en-us/troubleshoot/browsers/enhanced-security-configuration-faq) for at få flere oplysninger.


---

# 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/knowledge-base/troubleshooting-articles/documentation-tab-is-empty.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.