> 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/pam/es/pam-with-remote-desktop-manager/privileged-session-monitoring.md).

# Supervisión de sesiones privilegiadas

Supervise, observe y detenga sesiones privilegiadas activas, y revise grabaciones de sesiones anteriores, en el panel de supervisión de Remote Desktop Manager.

Ubicado en la pestaña ***Administration*** de Remote Desktop Manager Windows, el panel ***Privileged session monitoring*** le permite hacer un seguimiento, observar e incluso detener las sesiones privilegiadas activas. De forma predeterminada, solo los administradores tienen derechos para usar esta función. Para dar acceso a otros usuarios, diríjase a ***Administration*** – ***System permissions*** – ***Modules***, y establezca la opción en ***Allow*** (para todos los usuarios) o ***Custom*** (para usuarios o grupos de usuarios específicos).

Aquí también es donde se pueden ver y gestionar las grabaciones de sesiones anteriores. Las búsquedas se pueden filtrar por ***Date***, ***Vault***, ***Gateway***, ***Protocol***, ***User***, ***Gateway farm*** y ***Host***.

{% hint style="info" %}
El panel ***Privileged session monitoring*** solo está disponible con [Devolutions Server](https://devolutions.net/server/).
{% endhint %}


---

# 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/pam/es/pam-with-remote-desktop-manager/privileged-session-monitoring.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.