> 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/server/concepts/advanced-concepts/session-recording.md). # Session recording Session recording in Devolutions Server captures remote sessions via Devolutions Gateway, producing indexed video files reviewable from reports. Session recording in Devolutions Server captures what happens during remote sessions so privileged activity can be reviewed later. When configured with Devolutions Gateway and the recording server, selected vaults, folders, or entries can require recording, producing indexed video files that are available from reports or entry logs. Organizations often enable recording for high risk systems or PAM check-outs, allowing security teams to download or replay a session directly from the web interface when investigating an incident or validating that a third party followed agreed procedures. #### Related topics * [Configure recording server](/server/knowledge-base/how-to-articles/configure-recording-server.md) * [Download or view a recording session](/server/knowledge-base/how-to-articles/download-or-view-a-recording-session.md) * [Session recording](https://docs.devolutions.net/rdm/knowledge-base/how-to-articles/session-recording) --- # 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/server/concepts/advanced-concepts/session-recording.md?ask=&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.