> For the complete documentation index, see [llms.txt](https://docs.limio.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.limio.com/product/settings/security/track-changes.md).
# Track Changes
When you have a team working on your pages, it can become difficult to track edits and changes made to your drafts. You may also have auditing obligations. That's why we've integrated a Change Editor so that you can view the entire history of your site as it develops.
To access the Change Editor, you need to first choose your page or offer.
**On a Page or an Offer:**
**Step 1/2** - Click the arrow in the top right-hand corner to make the drop-down menu appear.
**Step 2/2** - Click on 'History'
You can now view all the changes made from contributors since its conception.
We suggest improving the readability further by choosing to view the Changes Editor in **Full Screen.**
To view further information about changes, click on the drop-down menu on the right next to the contributors. Each session contains timestamped edit history that is sorted left to right as Previous-->Current.
If you have any further questions, don't hesitate to message our team at .
---
# 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.limio.com/product/settings/security/track-changes.md?ask=&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.
.png?alt=media)
.png?alt=media)
.png?alt=media)