> 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/fr/pam-with-devolutions-server.md).

# PAM avec Devolutions Server

Découvrez Devolutions PAM dans Devolutions Server, offrant le stockage sécurisé des mots de passe, l'injection d'identifiants, le contrôle basé sur les rôles et l'authentification multifacteur intégré

[Devolutions Privileged Access Management](https://devolutions.net/privileged-access-management/) offre toutes les fonctionnalités suivantes. Il est spécifiquement conçu pour répondre aux besoins des PME, en proposant 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.

Voici quelques-unes de ses principales fonctionnalités :

* Facilité de déploiement et de gestion
* Coffre de mots de passe sécurisé
* Journalisation et rapports
* Authentification multifacteur intégrée
* Injection d'identifiants
* Contrôle d'accès basé sur les rôles

{% hint style="info" %}
Une licence est requise pour activer le module PAM. Veuillez contacter notre [département des ventes](mailto:sales@devolutions.net) pour plus d'informations sur la licence.
{% endhint %}

{% embed url="<https://youtu.be/38TkIsAAV0k>" %}


---

# 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/fr/pam-with-devolutions-server.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.