> For the complete documentation index, see [llms.txt](https://docs.meta-inf.hu/advanced-content-navigator/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.meta-inf.hu/advanced-content-navigator/cloud-users-guide/panels/page-history.md).

# Page History

### The Page History Panel

Keeping control over rapidly changing documentation is challenging in itself. Confluence keeps track of every change by creating a new version of the page in the [page history](https://support.atlassian.com/confluence-cloud/docs/create-edit-and-publish-a-page/#Page-versions-and-history). It is accessible from the page tree by opening the <mark style="color:green;">Page history pane</mark>l from the context menu.

### Finding *What* has Changed

After finding the [pages that have changed](/advanced-content-navigator/cloud-users-guide/show-changes-of-pages.md), the next big thing is to figure out what exactly has changed. This is where the app's <mark style="color:green;">smart page history</mark> comes into play with its <mark style="color:green;">What's changed since you last visited</mark> link.

This link intelligently determines the last page version the current user has seen and <mark style="color:green;">compares it with the current version</mark> of the page in Confluence's Page Comparison view.

<figure><img src="/files/QmwJZedtuWJqMatDrrQf" alt=""><figcaption><p>Compare the last seen version to the current one</p></figcaption></figure>

The Page History Panel recognizes pages you have not yet opened at all (<mark style="color:green;">pages new to the user</mark>) and shows a link in the history to open the current version of the page.

<figure><img src="/files/VCCrAuK6upOcwWPRmAs8" alt="" width="563"><figcaption><p>History of a page new to the user</p></figcaption></figure>


---

# 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.meta-inf.hu/advanced-content-navigator/cloud-users-guide/panels/page-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.