> 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/knowledge-base/knowledge-base-articles.md).

# Articles de la base de connaissances

Parcourez les articles de la Base de connaissances de Devolutions PAM portant sur les intégrations Ansible et Terraform, les scripts d'action de fournisseurs personnalisés et les intégrations partenai

Cette section regroupe la documentation de référence pour les intégrations et les capacités les plus techniques de PAM. Si vous automatisez votre configuration PAM, vous y trouverez des directives sur le module Ansible et le fournisseur Terraform, ainsi que les paquets requis pour chaque action PAM. Pour les déploiements personnalisés, cette section documente les scripts d'action de fournisseur PAM personnalisé dans Devolutions Server, ainsi que l'External Secrets Operator et les limitations relatives à l'injection d'identifiants pour certains outils.

Vous y trouverez également des articles de référence pratiques, notamment comment restituer automatiquement un compte PAM à la fermeture d'une entrée, les méthodes disponibles pour utiliser des comptes PAM personnels dans Remote Desktop Manager et un survol des intégrations partenaires PAM.


---

# 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/knowledge-base/knowledge-base-articles.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.