> 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/pam-with-remote-desktop-manager/privileged-account-management.md).

# Privileged account management

Discover, import, and configure Devolutions PAM accounts and providers directly within Remote Desktop Manager, without opening the web console.

Devolutions PAM accounts can be discovered, imported, and configured directly within Remote Desktop Manager. This allows PAM users to manage providers and password propagation scripts, as well as discover and import accounts without needing to navigate to Devolutions Server's or Devolutions Cloud's web interface.

The ***Privileged account management*** feature can be found in ***Administration*** – ***Management*** – ***Privileged account management***.

The ***Privileged account management*** window contains all the discovered accounts on the current workspace, along with a few options to edit them and create new ones.

{% hint style="info" %}
In a Microsoft SQL Server workspace, administrators can preview account discovery without a PAM license. The scan runs locally from Remote Desktop Manager on a ***Domain user*** (Windows only) or ***Entra ID user*** provider, and the results show the privilege tier of each discovered account. The provider is not saved and the discovered accounts cannot be imported; importing requires a [native workspace](https://docs.devolutions.net/rdm/getting-started/workspaces/workspace-types/native-workspaces) such as Devolutions Server or Devolutions Cloud.

Consult the [Providers](/pam/pam-with-devolutions-server/providers.md) article for more information on how to set up and manage PAM providers.
{% 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/pam-with-remote-desktop-manager/privileged-account-management.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.