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

# Posthistorik

Følg posthistorikken i Devolutions Cloud for at gennemgå ændringer, gendanne tidligere versioner og eksportere revisionsrapporter til efterlevelse.

Posthistorik er den versionsstyrede registrering af ændringer i en post, herunder hvem der ændrede den, hvornår og hvad der blev ændret. I Devolutions Cloud kan De i sektionen Historik for en post gennemgå tidligere versioner, se hvilke egenskaber der blev ændret, og gendanne en tidligere tilstand, når der er behov for det.

På et bredere niveau kan administratorer i rapporten Historik administrere slettede poster på tværs af bokse, gendanne dem, når det er nødvendigt, og eksportere CSV-rapporter som revisionsdokumentation. Det hjælper med at påvise kontrol over livscyklussen for følsomme data, for eksempel når det skal dokumenteres, hvornår en delt VPN-legitimationsoplysning blev roteret eller fjernet.

#### Relaterede emner

* [Postsektion - Historik](/cloud/da/web-interface/entries/entry-section/history.md)
* [Rapporter - Historik](/cloud/da/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/da/concepts/advanced-concepts/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.