> 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/cloud/concepts/intermediate-concepts/documentation.md). # Documentation Devolutions Cloud documentation fields store Markdown runbooks and notes alongside credentials, viewable in the web app and Remote Desktop Manager. Documentation in entries is a rich-text or markdown notes area used to store procedures, context, and troubleshooting information alongside credentials or connection data. This keeps how-to steps, escalation details, and business context attached directly to the system or credential instead of scattered in external wikis. In Devolutions Cloud, the Documentation section uses Markdown, supported by formatting helpers and a preview, so teams can maintain runbooks and diagrams in a structured way. For example, you can document a safe restart procedure on a server entry and have it visible both in the web interface and in Remote Desktop Manager. #### Related topics * [Entry section](/cloud/web-interface/entries/entry-section.md) --- # 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/cloud/concepts/intermediate-concepts/documentation.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.