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

# Description

Set the description, tags, status, expiration date and time zone of an entry or a folder in Remote Desktop Manager from the Description section.

The ***Description*** section holds the information that describes an entry: its description, tags, status, expiration date and time zone. Depending on the entry type, it also holds the fields of information entries and the export options of documents. The section is available for sessions, macros/scripts/tools, synchronizers, folders, credentials, information entries, documents, contacts, PAM accounts and PAM providers. It is not available for the vault.

In the entry properties, select ***Common*** – ***Description***.

For PAM providers in a Devolutions Server workspace, only the ***Description*** and ***Time zone*** groups are shown.

### Description

<table><thead><tr><th width="220">SETTING</th><th>DESCRIPTION</th></tr></thead><tbody><tr><td><em><strong>Description</strong></em></td><td><p>Description of the entry. The <em><strong>Mode</strong></em> button next to the group title defines its format:</p><ul><li><em><strong>Text</strong></em>: plain text.</li><li><em><strong>Rich text editor (.docx / .rtf)</strong></em>: formatted text. Offered only when <em><strong>Allow RTF description</strong></em> is selected in <em><strong>Administration</strong></em> – <em><strong>Vault settings</strong></em> – <em><strong>Common</strong></em> – <em><strong>Settings</strong></em>, or when the description already uses this format.</li><li><em><strong>URL</strong></em>: a web address. Select <em><strong>Navigate URL</strong></em> to open it.</li></ul></td></tr></tbody></table>

### Tags

<table><thead><tr><th width="220">SETTING</th><th>DESCRIPTION</th></tr></thead><tbody><tr><td><em><strong>Tags</strong></em></td><td>Tags of the entry. Enter a tag, or select the browse button to pick existing tags. Select <strong>×</strong> on a tag to remove it. When tags are inherited from the parent folders, an icon lists them. See <a href="https://docs.devolutions.net/rdm/concepts/intermediate-concepts/tags.md">Tags</a>.</td></tr></tbody></table>

### Status

<table><thead><tr><th width="220">SETTING</th><th>DESCRIPTION</th></tr></thead><tbody><tr><td><em><strong>Status</strong></em></td><td>Status of the entry: <em><strong>Locked</strong></em>, <em><strong>Disabled</strong></em>, <em><strong>Warning</strong></em>, <em><strong>Expired</strong></em>, <em><strong>Archived</strong></em> or <em><strong>Broken</strong></em>. <em><strong>Remove status</strong></em> clears the status. See <a href="https://docs.devolutions.net/rdm/ribbon-menu-bar/home/status.md">Status</a>.</td></tr><tr><td><em><strong>Message</strong></em></td><td>Message shown with the status. Shown when the entry has a status. Read-only for entries that are pending approval, unless the user has the permission to manage the pending approval status.</td></tr></tbody></table>

### Expiration

<table><thead><tr><th width="220">SETTING</th><th>DESCRIPTION</th></tr></thead><tbody><tr><td><em><strong>Expires after</strong></em></td><td>Sets an expiration date on the entry. Enter the date, or select the browse button to pick it. On that date, the entry takes the <em><strong>Expired</strong></em> status. A new date in the future removes the <em><strong>Expired</strong></em> status. Not available for <em><strong>Driver’s license</strong></em> information entries and <em><strong>API key</strong></em> credentials, which have their own expiration date.</td></tr><tr><td><em><strong>Add to calendar</strong></em></td><td>Exports the expiration date to a calendar file (.ics).</td></tr><tr><td><em><strong>Set expired message</strong></em></td><td>Defines the message shown when the entry is expired.</td></tr><tr><td><em><strong>Notify for expiring entries</strong></em></td><td>Defines when users are notified that the entry is about to expire: <em><strong>Never</strong></em>, <em><strong>Inherited</strong></em> (the setting of the parent folder, shown next to the list), <em><strong>30 days before expiration</strong></em>, <em><strong>60 days before expiration</strong></em>, <em><strong>90 days before expiration</strong></em> or <em><strong>Custom</strong></em> (enter a number of days, from 0 to 365). Available with Devolutions Server workspaces.</td></tr></tbody></table>

For certificate documents and X.509 certificate credentials, the expiration date is read from the certificate. When the entry already has a different expiration date, Remote Desktop Manager asks which date to keep.

When the entry is created from a template whose ***Expiration mode*** is ***Expires in***, the expiration date is calculated from the [template settings](https://docs.devolutions.net/rdm/knowledge-base/knowledge-base-articles/entry-settings/common-settings/template-settings.md).

### Time zone

The time zone of the entry is shown as a clock in the [Overview](https://docs.devolutions.net/rdm/user-interface/content-area/dashboard/dashboard-tabs/overview.md) dashboard tab.

<table><thead><tr><th width="220">SETTING</th><th>DESCRIPTION</th></tr></thead><tbody><tr><td><em><strong>Mode</strong></em></td><td>Defines the time zone of the entry: <em><strong>Default</strong></em>, <em><strong>Current time zone</strong></em>, <em><strong>Custom</strong></em> or <em><strong>Inherited</strong></em>. <em><strong>Default</strong></em> and <em><strong>Inherited</strong></em> use the time zone of the closest parent folder that defines one, shown next to the list.</td></tr><tr><td><em><strong>Zone</strong></em></td><td>Time zone of the entry. Shown when <em><strong>Mode</strong></em> is set to <em><strong>Custom</strong></em>.</td></tr></tbody></table>

### Information

Shown for information entries.

<table><thead><tr><th width="220">SETTING</th><th>DESCRIPTION</th></tr></thead><tbody><tr><td><em><strong>Resource</strong></em></td><td>Host or resource the information applies to. Select the <em><strong>Resource</strong></em> label to rename it for this entry.</td></tr><tr><td><em><strong>Owner</strong></em></td><td>Person the information belongs to. Select the <em><strong>Owner</strong></em> label to rename it for this entry.</td></tr></tbody></table>

### Document

Shown for document entries and for X.509 certificate credentials.

<table><thead><tr><th width="220">SETTING</th><th>DESCRIPTION</th></tr></thead><tbody><tr><td><em><strong>Allow export</strong></em></td><td>Allows users to export the document of the entry.</td></tr><tr><td><em><strong>Password</strong></em></td><td>Password of the document, such as the password of a protected file or certificate. Shown for document entries only.</td></tr></tbody></table>

#### See also

* [Documents and attachments](https://docs.devolutions.net/rdm/concepts/basic-concepts/documents-and-attachments.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/description.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.
