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

# Risiko privilegierter Zugriffe

Weisen Sie in Devolutions Server- und Devolutions Cloud-Datenquellen Risikostufen für privilegierte Zugriffe für Anbieter vom Typ Domänenbenutzer und Entra ID-Benutzer zu und bearbeiten Sie diese.

In [Devolutions Server](/pam/de/pam-with-devolutions-server/privileged-access-risk.md)- und [Devolutions Cloud](/pam/de/pam-with-devolutions-cloud/privileged-access-risk.md)-Datenquellen wird den Anbietern ***Azure / Entra ID user*** und ***Domain user*** automatisch eine Risikostufe zugewiesen. Gehen Sie zu ***Administration*** – ***Privileged account management*** – ***Privileged access risk***, um neue Gruppen mit benutzerdefinierten Risikostufen hinzuzufügen oder die bestehenden zu bearbeiten.

### Siehe auch

* [Domänenbenutzer-Anbieter](/pam/de/pam-with-devolutions-server/providers/managed-providers/domain-user-provider.md) (Devolutions Server)
* [Entra ID-Benutzer-Anbieter](/pam/de/pam-with-devolutions-server/providers/managed-providers/entra-id-user-provider.md) (Devolutions Server)
* [Domänenbenutzer-Anbieter](/pam/de/pam-with-devolutions-cloud/providers/domain-user-provider.md) (Devolutions Cloud)
* [Entra ID-Benutzer-Anbieter](/pam/de/pam-with-devolutions-cloud/providers/entra-id-user-provider.md) (Devolutions Cloud)


---

# 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/de/pam-with-remote-desktop-manager/privileged-account-management/privileged-access-risk.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.