> 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/custom-record.md).

# Custom record

Configure the Custom record data entry in Remote Desktop Manager to store your own named fields as text, sensitive, numeric, or date/time values.

This article details the many settings and options available for ***Custom record*** data 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. This field is required.</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><p>How the entry opens:</p><ul><li><strong>Embedded (tabbed)</strong> — Opens the entry in a tab of the main window.</li><li><strong>Undocked</strong> — Opens the entry 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>

### General

<table><thead><tr><th width="220">SETTINGS</th><th>DESCRIPTION</th></tr></thead><tbody><tr><td><strong>Add field</strong></td><td>Add a field to the record. A field without a name is labeled <em><strong>Field #</strong></em> followed by its position. Click the name of a field to rename it.</td></tr><tr><td><strong>Move up</strong></td><td>Move the selected field up one position.</td></tr><tr><td><strong>Move down</strong></td><td>Move the selected field down one position.</td></tr><tr><td><strong>Value</strong></td><td>Enter the value of the field. The control depends on the field type: a text box, a masked password field, a number, or a date and time.</td></tr><tr><td><strong>•••</strong></td><td><p>Open the options of the field. In a Devolutions Hub data source, only <em><strong>Sensitive</strong></em> is offered as a field type, and new fields are sensitive.</p><ul><li><strong>Show copy button in action section</strong> — Show a copy button for this field in the action section. Up to three fields can show this button.</li><li><strong>Text</strong> — Store the value as plain text.</li><li><strong>Sensitive</strong> — Store the value as a masked, sensitive value.</li><li><strong>Numeric</strong> — Store the value as a whole number.</li><li><strong>Date/Time</strong> — Store the value as a date and a time.</li><li><strong>Delete</strong> — Remove the field from the record.</li></ul></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/custom-record.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.
