> For the complete documentation index, see [llms.txt](https://docs.inforiver.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.inforiver.com/working-with-inforiver/8.-commenting-and-collaboration/comments/track-changes.md). # Track changes Tracking changes in the report using an interactive, filterable, and comment-enabled audit log that captures date, time, user details, task status and more is essential for data governance. This gives information such as who commented on a specific data point, and when. a) Click 'View All Comments' from the 'Comments' drop-down.

b) A side panel opens, showing all the comments along with some filters.

c) Comments and tasks can be filtered by assignee, assignor, status, and time period. They can also be filtered to show only your threads or all threads.

d) In the below image, I have filtered my threads and tasks assigned to a specific user.

e) You can also filter tasks based on who assigned them.

f) Comments and tasks can be filtered using a date range by clicking on the 'Calendar' icon highlighted.

g) Header and cell-level comments are also categorized in the side panel as shown below.

In the next section, we'll cover the [general settings and comment digest](/working-with-inforiver/8.-commenting-and-collaboration/comments/comment-settings.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.inforiver.com/working-with-inforiver/8.-commenting-and-collaboration/comments/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.