> 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/fr/web-interface/administration/modules/privileged-access.md).

# Accès privilégié

Activez et licenciez le module Gestion des accès privilégiés dans Devolutions Server pour offrir une protection PAM de calibre entreprise aux petites et moyennes entreprises.

{% hint style="success" %}
Une licence est requise pour activer le module Gestion des accès privilégiés (PAM). Veuillez contacter notre [département des ventes](mailto:sales@devolutions.net) pour plus d'informations au sujet de la licence.
{% endhint %}

La solution de gestion des accès privilégiés (PAM) de Devolutions est spécialement conçue pour répondre aux besoins des PME, en fournissant des fonctionnalités de calibre entreprise afin d'offrir un niveau de protection habituellement réservé aux grandes organisations, tout en étant robuste, facile à déployer et abordable.

Pour plus d'informations et de l'aide sur la configuration, consultez la section [Gestion des accès privilégiés (PAM)](https://docs.devolutions.net/pam/fr/pam-with-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/fr/web-interface/administration/modules/privileged-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.