> 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

Enable session recording in Remote Desktop Manager to capture video logs of remote connections at the vault, folder, or entry level.

A session recording provides a record of what a user did while a remote connection was opened in Remote Desktop Manager. By default, it records one frame per second and creates a video in `.webm` format. SSH Shell and Telnet sessions are recorded in the format set in ***SSH recording mode***: ***Terminal playback (.trp)*** by default, ***Asciicast (.cast)*** or ***Video (.webm)***. The frame rate and the SSH recording mode are set in the ***Recording*** section of the application settings (***File*** – ***Settings*** – ***Application*** – ***Recording*** on Windows and Linux), unless the workspace settings define them.

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. A session that requires recording cannot be opened externally.
{% endhint %}

### Supported sessions

* Active Directory dashboard
* Apple Remote Desktop
* Azure Blob Storage
* Dell iDRAC
* FTP (Windows and Linux)
* HP iLO
* Raw (Terminal)
* RDP
* RDP over Delinea Secret Server Proxy
* S3
* SCP (Windows and Linux)
* SFTP (Windows and Linux)
* SSH over Delinea Secret Server Proxy
* SSH Shell
* Telnet
* TN3270
* TN5250
* VNC, except with the UltraVNC library
* WebDAV
* Website, except with the Internet Explorer engine

### Configure session recording

1. Open ***Administration*** – ***Vault settings***, or the ***Properties*** of a folder or an entry.
2. Select ***Security*** – ***Session recording***. If the section is not shown, select ***Show all properties***.
3. Choose a ***Mode***.

| MODE                          | DESCRIPTION                                                                                                                         |
| ----------------------------- | ----------------------------------------------------------------------------------------------------------------------------------- |
| **Default (Inherited)**       | Uses the value of the parent folder, up to the vault. At the vault level, ***Default (Never)***.                                    |
| **Optional**                  | User is prompted to record when they open the session. If they decline, the session still opens.                                    |
| **Required**                  | Recording starts automatically. If the recording cannot start, the session does not open.                                           |
| **Required (when supported)** | Recording starts automatically on the platforms that support session recording. On the others, the session opens without recording. |
| **Never**                     | Session recording is turned off.                                                                                                    |
| **Root**                      | Uses the value of the vault. Not offered at the vault level.                                                                        |

4. With a Devolutions Server or Devolutions Cloud workspace, choose the ***Recording*** method: ***Local*** to save the recording with Remote Desktop Manager, or ***Remote*** to send it to the recording server of the workspace or to Devolutions Gateway.
5. With ***Remote***, choose the ***Gateway mode***. With ***Custom***, select the Devolutions Gateway that records the session in ***Gateway***. It can be a different gateway from the one used for the connection.
6. For a local recording, choose the ***Destination***: ***Default*** uses the value of the parent folder, up to the default recording folder of Remote Desktop Manager; ***Custom*** uses the folder entered in the field that appears.
7. Choose the ***Filename***: ***Connection log ID***, ***Entry name***, ***Entry Name + Date/Time*** or ***Custom***. At the vault level, the default is ***Entry Name + Date/Time***.
8. With ***Custom***, enter the filename, which can contain [variables](/rdm/concepts/intermediate-concepts/variables.md), or select ***Prompt for name*** to ask the user for the filename when the recording starts.
9. Save the changes.

Every setting of the section is described in [Session recording settings](/rdm/knowledge-base/knowledge-base-articles/entry-settings/common-settings/session-recording.md).

### Session recording all-in-one interface

The dashboard of the vault has a ***Recordings*** 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 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/how-to-articles/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.
