> For the complete documentation index, see [llms.txt](https://docs.struct.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.struct.com/tutorials/guides/how-to-use-the-changelog/how-to-navigate-the-changelog.md). # How to navigate the Changelog This short tutorial goes through how to navigate the changelog and find the transactions you are looking for. The changelog provides a record of all changes made to the system. While this is useful, it can be tricky to navigate. This quick guide will help you understand and navigate changelogs with ease. ### Where to find the changelog You can find the changelog by navigating to "Settings" > "Maintenance & Insights" > "System changelog". This section lists all changes made to entities in the system.

Opening the changelog will introduce you to a list of changelog entries. Each changelog entry is referred to as a transaction.

### How to view a transaction To view a transaction, hover over a changelog transaction and click the eye icon that appears on the right. This will display the transaction’s details, which may include a single change or multiple changes made in that transaction.

You can also view the changes made to each entity in a transaction. You can do this by clicking 'View changelog changes' on the entity.

When you click "View changelog changes", it will display a rollback revision.

Here you can see the changes made as well as the expected result if you choose to perform a rollback. {% hint style="info" %} For more information on using the rollback feature, see [How to use Changelogs actions](/tutorials/guides/how-to-use-the-changelog/how-to-use-rollback-or-export-transactions-in-the-changelog.md#rollback-single-entity). {% endhint %} --- # 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.struct.com/tutorials/guides/how-to-use-the-changelog/how-to-navigate-the-changelog.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.