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

# Session recording

Configure session recording for an entry, a folder or a vault in Remote Desktop Manager, including its mode, gateway and file name.

The ***Session recording*** section defines whether the sessions opened from an entry are recorded, and where the recordings are saved.

Available for folders, for the vault, and for session entries whose type supports [session recording](https://docs.devolutions.net/rdm/knowledge-base/how-to-articles/session-recording.md). For a website entry, the section is also shown when the entry is set to open in embedded mode. In the entry properties, select ***Security*** – ***Session recording***. By default, the section is shown only when ***Show all properties*** is selected in the entry properties.

The section is not shown when the ***Disable session recording*** [policy](https://docs.devolutions.net/rdm/knowledge-base/how-to-articles/apply-policies-gpos.md) is applied. With Devolutions Server and Devolutions Cloud, the settings can be changed only by users with the ***Edit session recording configuration*** permission. With [batch edit](https://docs.devolutions.net/rdm/ribbon-menu-bar/edit/batch-edit.md), select ***Override session recording*** 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:

* ***Default*** uses the value of the parent folder, up to the vault. It is shown as ***Default (Inherited)***.
* ***Root*** uses the value of the vault.

The value that applies is shown next to the setting. At the vault level, ***Root*** is not offered and ***Default*** shows the value it applies.

### Session recording

<table><thead><tr><th width="220">SETTING</th><th>DESCRIPTION</th></tr></thead><tbody><tr><td><em><strong>Mode</strong></em></td><td><p>Defines whether the session is recorded:</p><ul><li><em><strong>Default</strong></em>: the value of the parent folder. At the vault level, <em><strong>Default (Never)</strong></em>.</li><li><em><strong>Optional</strong></em>: the user is asked whether to record the session when it opens.</li><li><em><strong>Required</strong></em>: the session is recorded. The session does not open if the recording cannot start.</li><li><em><strong>Required (when supported)</strong></em>: the session is recorded on the platforms that support session recording, and opens without recording on the others.</li><li><em><strong>Never</strong></em>: the session is not recorded.</li><li><em><strong>Root</strong></em>: the value of the vault.</li></ul><p>With <em><strong>Required</strong></em> and <em><strong>Required (when supported)</strong></em>, the workspace can show a confirmation message before the entry opens. See <a href="https://docs.devolutions.net/rdm/knowledge-base/how-to-articles/session-recording.md#notify-users-that-their-session-is-recorded">Notify users that their session is recorded</a>.</p></td></tr><tr><td><em><strong>Recording</strong></em></td><td><p>Defines where the recording is made: <em><strong>Default</strong></em>, <em><strong>Local</strong></em>, <em><strong>Remote</strong></em> or <em><strong>Root</strong></em>. At the vault level, <em><strong>Default (Local)</strong></em>.</p><ul><li><em><strong>Local</strong></em>: the recording is saved by Remote Desktop Manager, according to the settings of the <em><strong>Local</strong></em> group.</li><li><em><strong>Remote</strong></em>: the recording is sent to the recording server of the workspace or to Devolutions Gateway. Offered when the recording server or the Devolutions Gateway recording is enabled in the workspace settings, and not for entries in the user vault.</li></ul><p>Shown with Devolutions Server and Devolutions Cloud workspaces, except for entries in the user vault. For an entry, hidden when <em><strong>Mode</strong></em> is <em><strong>Never</strong></em>. On a folder or the vault, a warning icon next to <em><strong>Remote</strong></em> indicates that the remote settings are handled separately from the local settings.</p></td></tr><tr><td><em><strong>Gateway mode</strong></em></td><td><p>Defines the Devolutions Gateway used for a remote recording:</p><ul><li><em><strong>Default</strong></em>: the value of the parent folder. At the vault level, the gateway used by the session.</li><li><em><strong>Custom</strong></em>: the gateway selected in the <em><strong>Gateway</strong></em> list.</li><li><em><strong>Root</strong></em>: the value of the vault. Not offered at the vault level.</li><li><em><strong>Same as session</strong></em>: the gateway used by the session. Not offered at the vault level.</li></ul><p>Shown with Devolutions Server and Devolutions Cloud workspaces, except for entries in the user vault. For an entry, hidden when <em><strong>Mode</strong></em> is <em><strong>Never</strong></em> or <em><strong>Recording</strong></em> is <em><strong>Local</strong></em>.</p></td></tr><tr><td><em><strong>Gateway</strong></em></td><td>Devolutions Gateway that records the session, shown when <em><strong>Gateway mode</strong></em> is <em><strong>Custom</strong></em>. A gateway must be selected. When the recording gateway is not the gateway used for the connection, the session cannot be stopped if the recording fails, even when the recording is required.</td></tr><tr><td><em><strong>Check health</strong></em></td><td>Checks the state of the selected gateway and its connection to the server, and shows the result. Shown when <em><strong>Gateway mode</strong></em> is <em><strong>Custom</strong></em>.</td></tr></tbody></table>

### Local

The group is shown on folders and on the vault. For an entry, it is shown when ***Mode*** is not ***Never*** and the recording is not remote.

<table><thead><tr><th width="220">SETTING</th><th>DESCRIPTION</th></tr></thead><tbody><tr><td><em><strong>Destination</strong></em></td><td>Folder where the recording files are saved: <em><strong>Default</strong></em>, <em><strong>Custom</strong></em> or <em><strong>Root</strong></em>. At the vault level, <em><strong>Default</strong></em> uses the default recording folder of Remote Desktop Manager. With <em><strong>Custom</strong></em>, enter or browse to the folder in the field that appears. The folder is required and cannot contain characters that are invalid in a path.</td></tr><tr><td><em><strong>Filename</strong></em></td><td><p>Name of the recording files:</p><ul><li><em><strong>Default</strong></em>: the value of the parent folder. At the vault level, <em><strong>Default (Entry Name + Date/Time)</strong></em>.</li><li><em><strong>Connection log ID</strong></em>: the identifier of the connection log.</li><li><em><strong>Entry name</strong></em>: the name of the entry.</li><li><em><strong>Entry Name + Date/Time</strong></em>: the name of the entry followed by the date and time of the recording.</li><li><em><strong>Custom</strong></em>: the name entered in the field that appears. The name cannot contain characters that are invalid in a filename.</li><li><em><strong>Root</strong></em>: the value of the vault. Not offered at the vault level.</li></ul></td></tr><tr><td><em><strong>Prompt for name</strong></em></td><td>Asks the user for the filename when the recording starts. Shown when <em><strong>Filename</strong></em> is <em><strong>Custom</strong></em>. When this option is cleared, the custom filename is required.</td></tr><tr><td><em><strong>File upload mode</strong></em></td><td><p>Defines how the recording files are saved to the destination when the session closes: <em><strong>Default</strong></em>, <em><strong>Root</strong></em>, <em><strong>Normal</strong></em> or <em><strong>Upload in background</strong></em>. At the vault level, <em><strong>Default (Normal)</strong></em>.</p><p>With <em><strong>Upload in background</strong></em>, the files are saved in the background and the progress is shown in the status bar.</p></td></tr></tbody></table>

See [Session recording](https://docs.devolutions.net/rdm/concepts/advanced-concepts/session-recording.md) for an overview of the feature.


---

# 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/session-recording.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.
