> 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/knowledge-base.md). # Knowledge base Introduces the Devolutions Server knowledge base, covering how-to guides, internal operations references, and troubleshooting fixes for common errors. Devolutions Server's knowledge base brings together the practical material you'll need once your instance is up and running: step-by-step how-tos, reference articles on server internals and operations, and fixes for the errors you're most likely to run into. * [How-to articles](/server/knowledge-base/how-to-articles.md) walk you through administrative tasks such as deploying and upgrading your server, configuring authentication and identity providers, securing your instance, and managing entries, vaults, and API access. * [Knowledge base articles](/server/knowledge-base/knowledge-base-articles.md) document server internals and operational practices, things like the security dashboard, the scheduler service, and the network requirements your server depends on. * [Troubleshooting articles](/server/knowledge-base/troubleshooting-articles.md) cover fixes for common errors, from login and authentication issues to IIS problems and database connectivity. --- # 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/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.