> 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/concepts/basic-concepts/information.md). # Information Information entries in Devolutions Server store reference data such as procedures, contacts, or asset details alongside credentials and documents. Information entries in Devolutions Server are flexible records for storing reference data that is not a remote session or standalone credential, such as procedures, contacts, or asset details. They live alongside other entries in business oriented vaults, share the same permission model, and can be combined with documents, attachments, and custom fields to build lightweight knowledge articles. Using information entries instead of separate wikis keeps operational context close to the passwords and connections your teams actually use. A typical use case is an information entry that documents a server, with links to its RDP and SSH entries plus notes about maintenance windows. #### Related topics * [Entries](/server/web-interface/vaults/entries.md) * [Vault content types](/server/web-interface/customization/vault-content-types.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/server/concepts/basic-concepts/information.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.