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

# Posthistorik

Posthistorik i Devolutions Server registrerer hver ændring af en post med tidsstempler og forfattere, så administratorer kan sammenligne versioner og rulle tilbage.

Posthistorik i Devolutions Server bevarer tidligere versioner af en post, så De kan se, hvem der ændrede hvad, og rulle sikkert tilbage. Hver ændring opretter en ny version med tidsstempel, forfatter og data for nøglefeltet, og fra sektionen Posthistorik kan De se, sammenligne, eksportere eller fjerne versioner i henhold til Deres rettigheder. (docs.devolutions.net)

Posthistorik er især nyttig, når forbindelsesindstillinger eller dokumentation overskrives: en administrator kan sammenligne versioner side om side og derefter vende tilbage til en sidst kendt god tilstand i stedet for at genopbygge posten fra bunden.

#### Relaterede emner

* [Posthistorik](/server/da/web-interface/vaults/entries/entry-section/entry-history.md)
* [Logge (postsektion)](/server/da/web-interface/vaults/entries/entry-section/logs.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/server/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.