> 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/es/concepts/advanced-concepts/entry-history.md).

# Historial de entradas

El historial de entradas es el registro versionado de los cambios realizados en una entrada, incluidos quién la modificó, cuándo y qué se cambió. En Devolutions Cloud, la sección Historial de una entrada le permite revisar versiones anteriores, comprender qué propiedades cambiaron y restaurar un estado anterior cuando sea necesario.

A un nivel más amplio, el informe Historial permite a los administradores gestionar las entradas eliminadas en todas las bóvedas, restaurarlas cuando sea necesario y exportar informes CSV como evidencia de auditoría. Esto ayuda a demostrar el control sobre los ciclos de vida de los datos sensibles, por ejemplo, al probar cuándo se rotó o eliminó una credencial VPN compartida.

#### Temas relacionados

* [Sección de entrada - Historial](/cloud/es/web-interface/entries/entry-section/history.md)
* [Informes - Historial](/cloud/es/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 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/es/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.