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

# Session recording

A session recording provides a record of what a user did while a remote connection was opened in Remote Desktop Manager. It records one frame per second and creates a video in `.webm` format.

You can configure session recording at the vault, folder or entry level and they can be optional or required.

{% hint style="warning" %}
Session recording is only available in embedded mode.
{% endhint %}

### Supported sessions

* Apple Remote Desktop
* Azure Blob Storage
* Chrome
* FTP
* Google Drive
* RDP
* S3
* SCP
* SFTP
* SSH Shell
* Telnet
* VNC
* WebDav
* Dell iDRAC
* HP iLO
* RDP over Delinea Secret Server Proxy
* SSH over Delinea Secret Server Proxy
* TN3270
* TN5250
* Website

### Configure session recording

1. Open ***vault Settings*** or ***Properties*** at folder or entry level.
2. In the ***Security*** section, click ***Session recording***.
3. Choose a ***Mode***.

| MODE                          | DESCRIPTION                                                                                                                          |
| ----------------------------- | ------------------------------------------------------------------------------------------------------------------------------------ |
| **Inherited**                 | Setting is inherited from parent folder.                                                                                             |
| **Optional**                  | User is prompted to record when they open the session. If they decline, the session still opens.                                     |
| **Required**                  | Recording starts automatically. If there is an issue with recording the session does not open.                                       |
| **Required (When supported)** | Recording starts automatically. If there is an issue with the recording, the session will launch and no recording will be available. |
| **Never**                     | Session recording is turned off.                                                                                                     |
| **Root (Default)**            | Refers to vault. Default on vault means ***Never***.                                                                                 |

4. Choose the ***Recording*** method.

   <div data-gb-custom-block data-tag="hint" data-style="success" class="hint hint-success"><p>Some options are only available with a Devolutions Server workspace.</p></div>

   | RECORDING METHOD   | DESCRIPTION                                                                                                                                                                         |
   | ------------------ | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
   | **Inherited**      | Setting is inherited from parent folder.                                                                                                                                            |
   | **Local**          | The recording files will be saved locally according to the ***Destination*** and ***Filename*** parameters below.                                                                   |
   | **Remote**         | The recording sessions will be managed by the ***Recording server***. All following options will no longer be available.                                                            |
   | **Gateway mode**   | When ***Remote*** is selected, you can choose a Devolutions Gateway for the recording. Note that a different Gateway from the one used for the connection can be set for recording. |
   | **Root (Default)** | Refers to root.                                                                                                                                                                     |
5. Choose the file ***Destination***.

   <div data-gb-custom-block data-tag="hint" data-style="info" class="hint hint-info"><p>By default, the file saves locally, not in the database.</p><p>We recommend choosing a custom file extension, for example on a shared network.</p></div>

* ***Inherited***: Setting is inherited from parent folder.
* ***Custom***: Paste the file destination path in the ***Destination*** box.
* ***Root (Default)***: Saves in Local App Data or in the workspace folder if you are using a ZIP file of Remote Desktop Manager.

6. Choose a ***Filename template*** or ***Prompt for name*** when user starts recording.

* ***Inherited***: Setting is inherited from parent folder.
* ***Connection Log ID***: Uses a multi-digit and letter identification number.
* ***Entry name***: Automatically use the entry name.
* ***Entry name + Date/Time***: Automatically use the entry name with the date and time of the recording.
* ***Root (Default)***: Use the entry name and the date and time of the recording.
* ***Custom***: Customize the file name.
  * Choose ***Always prompt for name*** to ask users to name the recording.
  * Use variables to customize the file name. Click the ***Variables*** button to view more information about available variables for this specific entry.

    <figure><img src="https://cdnweb.devolutions.net/docs/docs_en_kb_KB6158.png" alt=""><figcaption></figcaption></figure>

Two files are saved after the session is closed. The .webm file is the recording and the .dat is for the Remote Desktop Manager player.

### Session recording all-in-one interface

The ***Root dashboard*** has a dedicated tab that provides an all-in-one interface for viewing and downloading all recordings for supported sessions.

Recordings can also be accessed by right-clicking on the entry and selecting ***View*** – ***Recordings***.


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://docs.devolutions.net/rdm/knowledge-base/how-to-articles/session-recording.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.
