> 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/resources/other-resources.md). # Other resources Browse other Devolutions resources covering account recovery, certificate setup, license management, and product life cycle policies. This section gathers practical odds and ends that don't fit neatly into product-specific documentation, the kind of thing you would look up once and then forget about until you need it again. If you're locked out or something isn't loading right, you'll find help recovering your Devolutions Account, fixing a login page that won't open in your browser, and clearing your browser's local storage. For certificates and security, this section walks you through generating self-signed server and client certificates with OpenSSL, installing root certificates, and verifying a downloaded file's integrity using its SHA-256 hash. You'll also find guidance on the business side of things: understanding your license, renewing it, and troubleshooting common licensing issues, along with Devolutions' life cycle policies so you know how long a given release stays supported. Rounding things out are a few reference points worth knowing about such as recent terminology changes across Devolutions products, why it's important to keep major and minor versions matched across your tools, and how vault privacy works for administrators and users. --- # 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/resources/other-resources.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.