> 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

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](https://docs.devolutions.net/cloud/web-interface/entries/entry-section/history/)
* [Reports - History](https://docs.devolutions.net/cloud/web-interface/reports/history/)


---

# 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, and the optional `goal` query parameter:

```
GET https://docs.devolutions.net/cloud/concepts/advanced-concepts/entry-history.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.