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

# Overvågning af privilegerede sessioner

Overvåg, skyg og stop aktive privilegerede sessioner, og gennemgå tidligere sessionsoptagelser i overvågningsdashboardet i Remote Desktop Manager.

Dashboardet ***Overvågning af privilegerede sessioner***, som findes under fanen ***Administration*** i Remote Desktop Manager til Windows, giver Dem mulighed for at følge, skygge og endda stoppe aktive privilegerede sessioner. Som standard er det kun administratorer, der har rettigheder til at bruge denne funktion. For at give andre brugere adgang skal De gå til ***Administration*** – ***Systemtilladelser*** – ***Moduler*** og sætte indstillingen til ***Tillad*** (for alle brugere) eller ***Brugerdefineret*** (for bestemte brugere eller brugergrupper).

Her kan optagelser af tidligere sessioner også ses og administreres. Søgninger kan filtreres efter ***Dato***, ***Boks***, ***Gateway***, ***Protokol***, ***Bruger***, ***Gateway-farm*** og ***Vært***.

{% hint style="info" %}
Dashboardet ***Overvågning af privilegerede sessioner*** er kun tilgængeligt med [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/da/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.