> 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/ribbon-menu-bar/administration/system-settings/vault-management/security-settings.md).

# Security settings

Configure workspace security options in Remote Desktop Manager, including multifactor enforcement, Duo integration, time-based usage, and risky events.

The ***Security settings*** of the ***System settings*** apply to the whole workspace. To open them, go to ***Administration*** – ***System settings*** – ***Security settings***.

{% hint style="info" %}
The available settings vary based on the workspace type. A setting that a group policy controls cannot be changed here.
{% endhint %}

### Security

<table><thead><tr><th width="260">SETTING</th><th>DESCRIPTION</th></tr></thead><tbody><tr><td><em><strong>Create vault with restricted access by default</strong></em></td><td>Sets the inherited permissions of each new vault to <em><strong>Never</strong></em>, so that only the users and user groups granted access afterwards can use it. Does not apply to vaults created from a vault template.</td></tr><tr><td><em><strong>Force workspace multi-factor configuration</strong></em></td><td>Requires users to have a <a href="https://docs.devolutions.net/rdm/getting-started/workspaces/multifactor-authentication.md">multifactor configuration</a> on the workspace. Not shown with Devolutions Server, where multifactor authentication is configured on the server.</td></tr><tr><td><em><strong>Resolve credentials in overview</strong></em></td><td>Shows the username and password that come from a credential entry or a credential repository in the entry overview of the dashboard. Clear this option if resolving the credentials makes the overview slow to display.</td></tr><tr><td><em><strong>Allow host override</strong></em></td><td>Allows the host of a session to be overridden when it is opened. Windows only.</td></tr><tr><td><em><strong>Disable web browser developer tools</strong></em></td><td>Blocks the developer tools of the embedded web browser in the sessions of the workspace. Windows only.</td></tr><tr><td><em><strong>Disable website and web browser credential autofill after delay</strong></em></td><td>Stops the automatic filling of credentials in websites and web browser sessions after a delay.</td></tr><tr><td><em><strong>Hide port in RDP</strong></em></td><td>Hides the port of RDP sessions.</td></tr><tr><td><em><strong>Custom user password expiration</strong></em></td><td>Number of days after which custom users must change their password. <em><strong>0</strong></em> means the password does not expire. Shown with Microsoft SQL Server and Devolutions Server workspaces.</td></tr><tr><td><em><strong>Scan files for malware</strong></em></td><td>Scans attachments, documents, secure message files and files transferred in file explorer sessions, and defines what happens when a file is detected as harmful: <em><strong>Default (Warn)</strong></em>, <em><strong>Warn</strong></em>, <em><strong>Block</strong></em> or <em><strong>Disabled</strong></em>. Windows only.</td></tr><tr><td><em><strong>Allow Password Manager browser extension auto-fill</strong></em></td><td>Defines whether the Devolutions Password Manager browser extension can fill credentials from the workspace: <em><strong>Default (Enabled)</strong></em> or <em><strong>Disabled</strong></em>.</td></tr></tbody></table>

### Default Duo settings

<table><thead><tr><th width="260">SETTING</th><th>DESCRIPTION</th></tr></thead><tbody><tr><td><em><strong>Integration key</strong></em></td><td>Integration key of the Duo application. Select <em><strong>Check</strong></em> to test the Duo configuration.</td></tr><tr><td><em><strong>Secret key</strong></em></td><td>Secret key of the Duo application.</td></tr><tr><td><em><strong>API hostname</strong></em></td><td>API hostname of the Duo application.</td></tr></tbody></table>

### Time-based usage

These settings define the days and hours during which the entries of the workspace can be used. Entries, folders and vaults set to ***Workspace***, or that inherit up to the system settings, use these values. Time-based usage is enforced with Devolutions Server and Microsoft SQL Server workspaces. For the settings of an entry, a folder or a vault, see [Security settings](https://docs.devolutions.net/rdm/knowledge-base/knowledge-base-articles/entry-settings/common-settings/security-settings.md).

<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 entries can be used:</p><ul><li><em><strong>Any day</strong></em>: every day of the week.</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.</li></ul></td></tr><tr><td><em><strong>Time</strong></em></td><td><p>Hours during which the entries can be used on the allowed days:</p><ul><li><em><strong>Anytime</strong></em>: at any hour.</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>Time zone</strong></em></td><td>Time zone used to evaluate the time-based usage of every entry of the workspace, whatever the time zone of the users.</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></tbody></table>

### Events settings

<table><thead><tr><th width="260">SETTING</th><th>DESCRIPTION</th></tr></thead><tbody><tr><td><em><strong>Session events</strong></em></td><td><p>Defines whether the events of the entries can run. Some events, such as running an external program or a script, are risky if a malicious actor modifies them.</p><ul><li><em><strong>Default</strong></em>: uses the value of the application settings, shown in parentheses.</li><li><em><strong>Enabled</strong></em>: all events run.</li><li><em><strong>Warn on risky events</strong></em>: users are warned before a risky event runs.</li><li><em><strong>Disable risky events</strong></em>: risky events do not run.</li><li><em><strong>Disable all events</strong></em>: no event runs.</li><li><em><strong>Optional per vault</strong></em>: each vault defines its own value in its <a href="https://docs.devolutions.net/rdm/knowledge-base/knowledge-base-articles/entry-settings/common-settings/security-settings.md">security settings</a>.</li></ul></td></tr></tbody></table>

### My account settings

<table><thead><tr><th width="260">SETTING</th><th>DESCRIPTION</th></tr></thead><tbody><tr><td><em><strong>Forced save location</strong></em></td><td>Defines where <em><strong>My account settings</strong></em> are saved for all users: <em><strong>None</strong></em> (each user chooses), <em><strong>Database</strong></em> or <em><strong>Local</strong></em>. Shown only with workspaces that can save account settings in the database.</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/ribbon-menu-bar/administration/system-settings/vault-management/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.
