> 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/advanced-concepts/entry-history.md). # Entry history Track entry history in Devolutions Cloud to review changes, restore prior versions, and export audit reports for compliance. Entry history is the versioned record of changes made to an entry, including who modified it, when, and what was changed. In Devolutions Cloud, the History section of an entry lets you review previous versions, understand which properties changed, and restore an earlier state when needed. At a broader level, the History report lets administrators manage deleted entries across vaults, restore them when necessary, and export CSV reports for audit evidence. This helps demonstrate control over sensitive data lifecycles, for example when proving when a shared VPN credential was rotated or removed. #### Related topics * [Entry section - History](/cloud/web-interface/entries/entry-section/history.md) * [Reports - History](/cloud/web-interface/reports/history.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/advanced-concepts/entry-history.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.