> For the complete documentation index, see [llms.txt](https://help.metaforms.ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.metaforms.ai/design-collaboration/comments-and-tracked-changes.md).

# Comments & tracked changes

## Comments

Comments attach to a question. To add a comment, do these steps:

1. Put the pointer on the question.
2. Select the comment icon (**Add comment**).
3. Type your comment, then press **Enter**.

Each comment thread has **Reply** and **Resolve**, plus an **Internal / Client** switch.

![A comment thread on a question, with the Internal / Client switch](https://1402057010-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FgtHd8o9ldznZ1hKHiZvc%2Fuploads%2FRQHCFuy7j3ZfrMHazcWn%2F23-comment-thread-v2.png?alt=media)

* **Internal**: only your team can see the comment. New comments are **Internal**.
* **Client**: your client can also see the comment and reply to it in their review link.

To see all comments, open the **Comments** tab (the speech bubble icon on the right). The tab has **Open**, **Resolved**, and **All** lists. A lock icon shows on internal comments, and a globe icon shows on comments that your client can see.

| Action                | Where                                                        | What it does                                                 |
| --------------------- | ------------------------------------------------------------ | ------------------------------------------------------------ |
| Reply                 | The thread, or the **Comments** tab                          | Adds a reply that everyone who can see the comment can read. |
| Resolve               | The thread, or the **Comments** tab                          | Moves the thread to **Resolved**.                            |
| Reopen                | The **⋯** menu on a resolved comment in the **Comments** tab | Moves the thread back to **Open**.                           |
| Delete                | The **⋯** menu in the **Comments** tab                       | Removes the comment.                                         |
| Change who can see it | The **Internal / Client** switch on the thread               | Shares the comment with your client, or hides it again.      |

## Tracked changes

The **Tracked Changes** tab (the branch icon on the right) shows each edit to the questionnaire: the edits of the AI Assistant, your edits, the edits of your teammates, and the edits of your client. Each edit shows who made it and when.

![The Tracked Changes tab with edits from the AI Assistant](https://1402057010-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FgtHd8o9ldznZ1hKHiZvc%2Fuploads%2FuL5QwmlHwlciun96oKuc%2F22-tracked-changes.png?alt=media)

* Select **All**, **Agent**, **People**, or **Me** to filter the list.
* Select **Show diff** on an edit to see the text before and after the change.
* Select **View at this step** to see the questionnaire as it was after that edit.
* Select **Revert** to undo an edit to a question.
* Edits that you did not see yet are highlighted in the draft. Select **Mark as read** when you have read them.

{% hint style="info" %}
Edits apply to the questionnaire immediately. There is no approval step. To undo an edit, use **Revert**. Each handoff shows in the list as a divider, for example **V1 Handoff**.
{% endhint %}

Next, [set up client access](/design-collaboration/setting-up-client-access.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://help.metaforms.ai/design-collaboration/comments-and-tracked-changes.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.