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

# Enregistrement de session

L'enregistrement de session dans Remote Desktop Manager capture l'activité des sessions à distance pour l'audit, les enquêtes et la révision de conformité dans l'ensemble des entrées.

L'enregistrement de session capture l'activité des sessions à distance prises en charge dans Remote Desktop Manager à des fins d'audit et de révision. Utilisez-le pour documenter les actions des administrateurs, appuyer les enquêtes et démontrer la conformité, tout en gardant les enregistrements liés aux entrées pertinentes.

Combinez les enregistrements avec des journaux et des rapports détaillés pour retracer qui a ouvert des sessions et à quel moment, puis tirez parti du contrôle d'accès basé sur les rôles (RBAC) pour vous assurer que seuls les utilisateurs autorisés peuvent lancer des sessions ou accéder aux enregistrements stockés.

#### Sujets connexes

* [Enregistrement de session](/rdm/fr/knowledge-base/how-to-articles/session-recording.md)

#### Voir aussi

* [Chemin d'enregistrement de Devolutions Gateway](https://docs.devolutions.net/gateway/fr/knowledge-base/knowledge-base-articles/devolutions-gateway-recording-path)


---

# 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/fr/concepts/advanced-concepts/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.
