> 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/concepts/privileged-remote-access.md).

# Privileged remote access

Privileged remote access in Devolutions PAM secures and monitors high-risk RDP, VNC, SSH, and HTTP/S sessions without exposing credentials to users.

**Privileged remote access** (PRA) enables organizations to securely manage and oversee high-risk [sessions](/pam/concepts/session-management.md) that use standard protocols like RDP, VNC, SSH, and HTTP/S. It ensures that only authorized users can initiate and interact with critical systems while maintaining complete visibility into what happens during those sessions.

In Devolutions products, this concept is primarily supported through Devolutions PAM, which works in combination with Remote Desktop Manager to broker access to remote resources without exposing credentials. Sessions can be launched interactively, automatically, or through scripting, and every session can be monitored, [recorded](/pam/concepts/session-recording.md), and audited for [compliance](/pam/concepts/compliance-reporting.md) and forensic analysis. Credential injection further secures access by preventing users from ever seeing the actual passwords.

This approach helps protect sensitive assets, streamline IT operations, and ensure compliance with internal and regulatory access control requirements.

#### Privileged remote access aliases

* PRA
* Privileged session management
* Remote privileged access
* Privileged user session monitoring

#### Related topics

* [External PAM integrations](https://docs.devolutions.net/rdm/concepts/advanced-concepts/external-pam-integrations)
* [Logs, reports, and audits](https://docs.devolutions.net/rdm/concepts/advanced-concepts/logs-reports-and-audits)
* [Session management](/pam/concepts/session-management.md)


---

# 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/concepts/privileged-remote-access.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.