> 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/basic-concepts/information.md).

# Information

Information entries in Devolutions Cloud centralize reference data such as contact details, asset identifiers, or policy notes in shareable, permission-controlled records. Unlike pure credential entries, an information entry focuses on descriptive fields, links, and documentation so teams can look up values like support contacts, door codes, serial numbers, or policy references alongside their passwords.

Because these entries live in the same vaults and inherit the same roles and permissions model, administrators can decide exactly who may view or edit sensitive information. A typical pattern is to store vendor contract information in an information entry and link it from the related privileged accounts, ensuring everyone troubleshooting an issue sees both operational details and business context.

#### Related topics

* [Entry type](https://docs.devolutions.net/cloud/web-interface/entries/entry-type/)
* [Create entries manually](https://docs.devolutions.net/cloud/web-interface/entries/create-entries-manually/)
* [Documentation](https://docs.devolutions.net/cloud/web-interface/entries/entry-section/documentation/)


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://docs.devolutions.net/cloud/concepts/basic-concepts/information.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.