> 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/rdm/knowledge-base.md). # Knowledge base Browse the Remote Desktop Manager knowledge base for how-to articles, reference material, and troubleshooting guides on entry types and platform behavior. *** The Knowledge base brings together task-oriented and reference content that goes beyond the core product documentation, organized into these three sections: * [How-to articles](/rdm/knowledge-base/how-to-articles.md) walk through specific configuration scenarios and integrations. * [Knowledge base articles](/rdm/knowledge-base/knowledge-base-articles.md) cover reference material on specific entry types and settings (SSH keys, API keys, certificates, synchronizers, password managers), along with background information on licensing, deprecated features, and platform behavior that doesn't fit neatly into a how-to format. * [Troubleshooting articles](/rdm/knowledge-base/troubleshooting-articles.md) document known issues and their resolutions including connection errors, authentication failures, performance problems, and error messages encountered across Windows, macOS, and Linux clients, as well as with specific integrations like CyberArk, Azure SQL, and various remote access protocols. --- # 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/rdm/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.