> 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/knowledge-base/knowledge-base-articles/entry-settings/documentation-editor.md).

# Documentation editor

Create Documentation editor document entries in Remote Desktop Manager to write documentation pages that are stored with the entry in the workspace.

This article details the settings available for ***Documentation editor*** document entries in Remote Desktop Manager. A ***Documentation editor*** entry holds documentation pages written in Remote Desktop Manager. When the entry opens, its documentation pages are displayed. For the documentation of other entries, see [Documentation](https://docs.devolutions.net/rdm/knowledge-base/knowledge-base-articles/entry-settings/common-settings/documentation.md).

{% hint style="info" %}
The ***Documentation editor*** entry type is offered only in workspaces that support documentation: Devolutions Server, Devolutions Cloud, Microsoft SQL Server, and SQLite databases created or upgraded by a recent version of Remote Desktop Manager.
{% endhint %}

<table data-header-hidden><thead><tr><th width="200"></th><th></th></tr></thead><tbody><tr><td><strong>SETTINGS</strong></td><td><strong>DESCRIPTION</strong></td></tr><tr><td><strong>Name</strong></td><td>The name of the entry.</td></tr><tr><td><strong>Folder</strong></td><td>The folder where the entry is located.</td></tr><tr><td><strong>Display</strong></td><td>How the documentation opens: <em><strong>Embedded (tabbed)</strong></em> or <em><strong>Undocked</strong></em>.</td></tr></tbody></table>

The entry type has no other settings. Its content is managed automatically: the documentation pages are stored in the data source with the entry, and are edited from the entry itself.


---

# 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/knowledge-base/knowledge-base-articles/entry-settings/documentation-editor.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.
