> 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/text-editor.md).

# Text editor

Configure Text editor document entries in Remote Desktop Manager, including the display mode, storage mode, a blank or uploaded document, and read-only mode.

This article details the many settings and options available for ***Text editor*** document entries in Remote Desktop Manager.

<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. Click the browse button to select a folder, or click the add (<em><strong>+</strong></em>) button to create a new one.</td></tr><tr><td><strong>Display</strong></td><td><p>How the document opens:</p><ul><li><strong>External</strong> — Opens the document outside of Remote Desktop Manager. Additional lists let you choose the monitor and the virtual desktop where the window opens.</li><li><strong>Embedded (tabbed)</strong> — Opens the document in a tab of the main window.</li><li><strong>Undocked</strong> — Opens the document in a separate window. Additional lists let you choose the monitor and the virtual desktop where the window opens.</li></ul><p>On Linux, the list also offers <em><strong>Default (inherited)</strong></em>, which uses the display mode of the nearest parent folder that sets one, otherwise the default of the entry type. The mode it resolves to is shown next to the list.</p></td></tr></tbody></table>

<table><thead><tr><th width="220">SETTINGS</th><th>DESCRIPTION</th></tr></thead><tbody><tr><td><strong>Mode</strong></td><td><p>Select where the document is kept:</p><ul><li><strong>Stored in database</strong> — The document is uploaded and stored with the entry. This is the default for new entries. This option is not offered when the data source does not support attachments, or when an existing entry uses another mode.</li><li><strong>Link to file</strong> — The entry points to a file on disk.</li><li><strong>URL</strong> — The entry points to a web address.</li></ul></td></tr><tr><td><strong>Source</strong></td><td><p>Shown when creating an entry stored in the database. Select how the document is provided:</p><ul><li><strong>Upload existing file</strong> — Uploads a file you select.</li><li><strong>Create empty document</strong> — Creates a blank document. This is the default for new entries. The blank file is created when you save, then opened for editing.</li></ul></td></tr><tr><td><strong>Filename</strong></td><td>With <em><strong>Stored in database</strong></em>, select the file to upload when creating the entry. With <em><strong>Link to file</strong></em>, enter or browse to the path of the file. For a document stored in the database, buttons appear beside the field. On a new entry that already holds a document, <em><strong>Clear</strong></em> deletes the stored document after a confirmation. On an existing entry, <em><strong>Update document</strong></em> replaces the document with another file, <em><strong>Save as</strong></em> exports a copy of the document, and <em><strong>Save and edit content</strong></em> saves the entry and opens the document for editing (Windows and Linux). When <em><strong>Read-only</strong></em> is checked, this button is named <em><strong>Save and open</strong></em>.</td></tr><tr><td><strong>Document name</strong></td><td>Shown when <em><strong>Source</strong></em> is set to <em><strong>Create empty document</strong></em>. Enter the name of the new document. The <code>.txt</code> extension is added automatically. When left empty, the entry name is used.</td></tr><tr><td><strong>URL</strong></td><td>Shown when the mode is <em><strong>URL</strong></em>. Enter the web address of the document. Click the <em><strong>Navigate URL</strong></em> button to open the address in your browser.</td></tr><tr><td><strong>Use default credentials</strong></td><td>Shown when the mode is <em><strong>URL</strong></em>. Uses the default credentials of the current user to access the URL.</td></tr><tr><td><strong>Read-only</strong></td><td>Opens the document in read-only mode. This option is unavailable when <em><strong>Source</strong></em> is set to <em><strong>Create empty document</strong></em>.</td></tr><tr><td><strong>File size</strong></td><td>The size of the document. This value is read-only.</td></tr><tr><td><strong>Created by</strong></td><td>The user who created the entry. This value is read-only.</td></tr><tr><td><strong>Creation date</strong></td><td>The date the entry was created. This value is read-only.</td></tr></tbody></table>


---

# 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/text-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.
