> 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/knowledge-base.md). # Knowledge base Explore the Devolutions PAM knowledge base for how-to guides, technical reference articles, and troubleshooting help with privileged access management. Devolutions PAM's knowledge base brings together the practical material you'll need once your privileged access management setup is running: step-by-step how-tos, reference articles on PAM's more technical capabilities, and fixes for issues you might encounter. * [How-to articles](/pam/knowledge-base/how-to-articles.md) walk you through configuring and deploying PAM provider, from Active Directory and Entra ID to custom domain accounts, along with day-to-day tasks like rotating passwords and elevating privileged access. * [Knowledge base articles](/pam/knowledge-base/knowledge-base-articles.md) cover more technical integrations and reference material, such as automation with Ansible and Terraform, custom provider action scripts, and partner integrations. * [Troubleshooting articles](/pam/knowledge-base/troubleshooting-articles.md) help you resolve issues that come up with custom PAM providers and their action scripts. --- # 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/knowledge-base.md?ask=&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.