> 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/external-pam-integrations.md).

# External PAM integrations

External PAM integrations connect Devolutions Server and Remote Desktop Manager to third party privileged access platforms for credential retrieval.

External PAM integrations let Devolutions Server and Remote Desktop Manager work with third party privileged access management platforms instead of storing all privileged credentials locally. Remote Desktop Manager requests credentials from the external PAM just in time and injects them into sessions, while Devolutions Server centralizes session brokering, approvals, and auditing of who used which account. (docs.devolutions.net)

This approach allows organizations that already rely on tools such as CyberArk or other PAM solutions to keep their existing credential lifecycle, while adopting Devolutions Server and Devolutions PAM as a unified access, logging, and policy enforcement layer.

#### Related topics

* [External PAM integrations](https://docs.devolutions.net/rdm/concepts/advanced-concepts/external-pam-integrations)
* [Devolutions PAM](https://docs.devolutions.net/pam)
* [PAM reports in Devolutions Server](https://docs.devolutions.net/pam/pam-with-devolutions-server/pam-reports-in-devolutions-server)


---

# 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/external-pam-integrations.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.
