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

# Security settings

Configure checkout, offline access, time-based usage, seal and temporary access for an entry, a folder or a vault in Remote Desktop Manager.

The ***Security settings*** section of an entry, a folder or a vault controls how and when users can use its content: checkout, offline access, time-based usage, password variables, session events, seal and temporary access. The section is the same on Windows, macOS and Linux.

To open it:

1. Open the properties of the entry or folder. For the vault itself, go to ***Administration*** – ***Vault settings***.
2. In the left menu, select ***Security*** – ***Security settings***.

By default, the section is hidden in the simplified view of the properties; select ***Show all properties*** to display it.

The groups shown depend on the workspace type, the entry type and the level being edited (entry, folder or vault). With [batch edit](https://docs.devolutions.net/rdm/ribbon-menu-bar/edit/batch-edit.md), select ***Override security*** to replace these settings on every selected entry.

### Values that come from a higher level

Most settings offer values that take their value from a higher level instead of setting one:

* ***Default*** and ***Inherited*** use the value of the parent folder, up to the vault.
* ***Root*** uses the value of the vault.
* ***Workspace*** uses the value set in ***Administration*** – ***System settings*** – ***Security settings***. The value in parentheses is the current system setting.

When one of these values is selected, the value that applies is shown in grey next to the setting. These values are not offered at the vault level, since the vault has no parent.

### General

These settings configure the [checkout system](https://docs.devolutions.net/rdm/ribbon-menu-bar/edit/checkout-system.md).

<table><thead><tr><th width="220">SETTING</th><th>DESCRIPTION</th></tr></thead><tbody><tr><td><em><strong>Checkout mode</strong></em></td><td>Defines whether the entry must be checked out before use: <em><strong>Not available</strong></em>, <em><strong>Automatic</strong></em>, <em><strong>Manual</strong></em> or <em><strong>Automatic (when supported)</strong></em>.</td></tr><tr><td><em><strong>Checkout prompt</strong></em></td><td>Defines whether users are prompted for a comment when they check out the entry: <em><strong>Yes</strong></em>, <em><strong>No</strong></em> or <em><strong>Yes (comment forced)</strong></em>. <em><strong>Yes (comment forced)</strong></em> is offered only when the workspace supports it.</td></tr><tr><td><em><strong>Multiple checkouts</strong></em></td><td>Defines how many users can check out the entry at the same time: <em><strong>Off</strong></em>, <em><strong>Infinite</strong></em> or <em><strong>Custom</strong></em> (enter the number of users). See <a href="https://docs.devolutions.net/rdm/knowledge-base/knowledge-base-articles/multiple-checkouts.md">Multiple checkouts</a>.</td></tr></tbody></table>

### Offline

These settings apply to workspaces that support [offline mode](https://docs.devolutions.net/rdm/getting-started/workspaces/offline-mode.md).

<table><thead><tr><th width="220">SETTING</th><th>DESCRIPTION</th></tr></thead><tbody><tr><td><em><strong>Allow offline</strong></em></td><td>Defines whether the entry is available in offline mode: <em><strong>Yes</strong></em> or <em><strong>No</strong></em>. At the vault level, the default value is <em><strong>Yes</strong></em>. Cannot be changed when the entry requires a checkout.</td></tr><tr><td><em><strong>Synchronize document offline</strong></em></td><td>For documents stored in the entry or in its attachments, defines whether the document is copied to the offline cache: <em><strong>No</strong></em>, <em><strong>Yes</strong></em> or <em><strong>Yes (ignore max file size)</strong></em>.</td></tr><tr><td><em><strong>Synchronize documentation offline</strong></em></td><td>Defines whether the documentation of the entry is copied to the offline cache: <em><strong>No</strong></em>, <em><strong>Yes</strong></em> or <em><strong>Yes (ignore max file size)</strong></em>.</td></tr></tbody></table>

### Time-based usage

Time-based usage restricts the days and the hours during which users can use an entry. The group is available with Devolutions Server and Microsoft SQL Server workspaces. It is shown for folders, for the vault, and for session entries; it is not shown for contact, document, credential, information, macro, synchronizer and PAM entries, nor in the user vault.

<table><thead><tr><th width="160">SETTING</th><th>DESCRIPTION</th></tr></thead><tbody><tr><td><em><strong>Days</strong></em></td><td><p>Days on which the entry can be used:</p><ul><li><em><strong>Any day</strong></em>: every day of the week.</li><li><em><strong>Workspace</strong></em>: the days set in the system settings.</li><li><em><strong>Inherited</strong></em>: the whole time-based usage configuration (days and hours) of the closest parent folder that has one, then of the vault, then of the system settings. Not offered at the vault level.</li><li><em><strong>Weekdays</strong></em>: Monday to Friday.</li><li><em><strong>Weekends</strong></em>: Saturday and Sunday.</li><li><em><strong>Custom</strong></em>: the days selected in the list that appears. At least one day must be selected.</li></ul><p>New entries and folders use <em><strong>Inherited</strong></em>. A vault with no configuration uses <em><strong>Workspace</strong></em>.</p></td></tr><tr><td><em><strong>Time</strong></em></td><td><p>Hours during which the entry can be used on the allowed days. Hidden when <em><strong>Days</strong></em> is set to <em><strong>Inherited</strong></em>.</p><ul><li><em><strong>Anytime</strong></em>: at any hour. This is the default value.</li><li><em><strong>Workspace</strong></em>: the hours set in the system settings.</li><li><em><strong>Custom</strong></em>: between the <em><strong>Start</strong></em> and <em><strong>End</strong></em> times.</li></ul></td></tr><tr><td><em><strong>Start</strong></em>, <em><strong>End</strong></em></td><td>Time range, in 24-hour format, when <em><strong>Time</strong></em> is set to <em><strong>Custom</strong></em>. The default values are 00:00 and 23:59. A range that ends earlier than it starts, such as 22:00 to 06:00, continues after midnight.</td></tr><tr><td><em><strong>Time zone</strong></em></td><td>Time zone used to evaluate the range, shown when <em><strong>Time</strong></em> is set to <em><strong>Custom</strong></em>. It is the time zone selected in <em><strong>Administration</strong></em> – <em><strong>System settings</strong></em> – <em><strong>Security settings</strong></em> and cannot be changed here.</td></tr></tbody></table>

Outside the allowed days and hours, Remote Desktop Manager shows the message ***\<entry name> cannot be opened at this time***. The restriction applies to:

* Opening the session.
* Viewing or copying the password and the other sensitive fields of the entry.
* Credential and information entries, which follow the time-based usage of their folder.
* Quick search, Devolutions Send, PAM and the mobile applications, which also enforce the rule.

The time used is the time of the workspace server, converted to the time zone of the system settings. If that time zone is not available, the local time zone of the computer is used.

In offline mode, an entry with any restriction other than ***Any day*** and ***Anytime*** cannot be opened, and Remote Desktop Manager shows the message ***\<entry name> is not available in offline mode due to the time-based usage configuration.***

Users with the ***Bypass time-based access*** permission, including vault owners, are not restricted.

With a Devolutions Server workspace, the same configuration is also available in the web interface of Devolutions Server.

### Password

<table><thead><tr><th width="220">SETTING</th><th>DESCRIPTION</th></tr></thead><tbody><tr><td><em><strong>Allow password in variable</strong></em></td><td>Allows the password of the entry to be used in variables, such as <code>$PASSWORD$</code> in macros and command lines. Available only to users who can view the password. Not shown for contact, document, information and PAM entries, nor for the vault. See <a href="https://docs.devolutions.net/rdm/knowledge-base/how-to-articles/allow-password-in-variable.md">Allow password in variable</a>.</td></tr></tbody></table>

### Events settings

<table><thead><tr><th width="220">SETTING</th><th>DESCRIPTION</th></tr></thead><tbody><tr><td><em><strong>Session events</strong></em></td><td>Defines whether the session events of the entries in the vault can run: <em><strong>Enabled</strong></em>, <em><strong>Warn on risky events</strong></em>, <em><strong>Disable risky events</strong></em> or <em><strong>Disable all events</strong></em>. Shown only at the vault level, and editable only when <em><strong>Session events</strong></em> is set to <em><strong>Optional per vault</strong></em> in the <a href="https://docs.devolutions.net/rdm/ribbon-menu-bar/administration/system-settings/vault-management/security-settings.md">system security settings</a>. Not available with Devolutions Cloud.</td></tr></tbody></table>

### Seal

<table><thead><tr><th width="220">SETTING</th><th>DESCRIPTION</th></tr></thead><tbody><tr><td><em><strong>Seal state</strong></em></td><td>Seals or unseals the entry: <em><strong>None</strong></em>, <em><strong>Sealed</strong></em> or <em><strong>Unsealed</strong></em>. Shown for credential and document entries with Devolutions Server workspaces that support sealed entries. See <a href="https://docs.devolutions.net/rdm/knowledge-base/how-to-articles/sealed-entries.md">Sealed entries</a>.</td></tr></tbody></table>

### Temporary access

<table><thead><tr><th width="220">SETTING</th><th>DESCRIPTION</th></tr></thead><tbody><tr><td><em><strong>Mode</strong></em></td><td>Defines whether users can request temporary access to the entry: <em><strong>Allowed</strong></em> or <em><strong>Denied</strong></em>.</td></tr><tr><td><em><strong>Authorizer</strong></em></td><td>Defines who can approve the requests: <em><strong>Administrator only</strong></em> or <em><strong>Custom</strong></em>. With <em><strong>Custom</strong></em>, select <em><strong>Add</strong></em> to add the users and user groups that can approve requests to the <em><strong>Authorizers</strong></em> list.</td></tr></tbody></table>

Temporary access is not available with Devolutions Cloud. See [Enable temporary access](https://docs.devolutions.net/rdm/knowledge-base/how-to-articles/enable-temporary-access.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/security-settings.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.
