> 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/rdm/user-interface/context-menu/entry-history.md).

# Entry history

View and compare different versions of session entries with Entry history in Remote Desktop Manager, and delete individual or full revision history.

The ***Entry history*** feature allows you to view details regarding different version of your sessions and also gives you the option of performing compares between different versions.

{% hint style="info" %}
This feature requires an [native workspace](/rdm/getting-started/workspaces/workspace-types/native-workspaces.md). Also, you must be an administrator of the workspace to perform this action.
{% endhint %}

### Settings

To display the entry history, right-click on an entry and select ***View – Entry History***.

#### Entry history view

The entry history view dialog allows you to compare two entries and manage history revisions. To compare simply select any two entries then use the ***Compare*** button. You can delete any history revision or the entire history using the ***Delete*** and ***Delete All*** buttons.

#### View Deleted Entries

Use the ***Administration – View deleted*** to [manage and restore deleted entries](/rdm/ribbon-menu-bar/administration/deleted-entries.md).

#### See also

* [Devolutions Academy - Managing Entry History and Recovery](https://academy.devolutions.net/student/path/1925316/activity/2667998)
* [Devolutions Academy - Manage entry history and restore previous versions in Remote Desktop Manager](https://academy.devolutions.net/student/activity/3612369-manage-entry-history-and-restore-previous-versions-in-remote-desktop-manager)


---

# 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/rdm/user-interface/context-menu/entry-history.md?ask=<question>&goal=<user_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.