> 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/common-settings/custom-fields.md).

# Custom fields

Add custom fields to an entry or a folder in Remote Desktop Manager, rename them, mark them as sensitive and add more than five fields.

The ***Custom fields*** section stores information that has no field of its own in the entry. Each field has a title and a value, and its value can be marked as sensitive. The section is available for sessions, macros/scripts/tools, synchronizers, folders, credentials, information entries, documents, contacts and PAM accounts. It is not available for PAM providers and for the vault.

In the entry properties, select ***Common*** – ***Custom fields***.

With [batch edit](https://docs.devolutions.net/rdm/ribbon-menu-bar/edit/batch-edit.md), select ***Override*** to replace the custom fields of every selected entry.

### Custom fields

The section shows five custom fields, titled ***Custom #1*** to ***Custom #5*** by default.

<table><thead><tr><th width="220">SETTING</th><th>DESCRIPTION</th></tr></thead><tbody><tr><td><em><strong>Title</strong></em></td><td>Name of the custom field. Replace the default title to name the field.</td></tr><tr><td><em><strong>Sensitive</strong></em></td><td>Masks the value of the field and protects it like a password. Available to users who can view sensitive information.</td></tr><tr><td><em><strong>Value</strong></em></td><td>Value of the field, on one or more lines. When the field is sensitive, the value is masked and can be revealed only by users who can view sensitive information.</td></tr><tr><td><em><strong>More custom fields</strong></em></td><td>Opens the <em><strong>More custom fields</strong></em> window, which holds the fields beyond the first five. Select <em><strong>Add</strong></em> to add a field, enter its <em><strong>Title</strong></em> and value, select <em><strong>Sensitive</strong></em> to mask it, and select the delete button to remove it. The number of additional fields is shown next to the link.</td></tr></tbody></table>

Users who are not allowed to view the information of entries see the fields with their default titles and no values, and their changes to the fields are not saved.

The first five custom fields can be made mandatory in the [template settings](https://docs.devolutions.net/rdm/knowledge-base/knowledge-base-articles/entry-settings/common-settings/template-settings.md) of a template. The vault settings can rename the navigation pane columns that show them, in the [User interface](https://docs.devolutions.net/rdm/knowledge-base/knowledge-base-articles/entry-settings/common-settings/user-interface.md) section of the vault.

#### See also

* [Custom fields](https://docs.devolutions.net/rdm/concepts/intermediate-concepts/custom-fields.md)
* [Copy buttons for custom fields](https://docs.devolutions.net/rdm/knowledge-base/how-to-articles/copy-buttons-for-custom-fields.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/knowledge-base/knowledge-base-articles/entry-settings/common-settings/custom-fields.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.
