> For the complete documentation index, see [llms.txt](https://docs.nested-knowledge.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.nested-knowledge.com/collaborate/comments.md).

# Comments

Learn how to make comments at the nest level and study level.

Comments keep your team's discussion inside the nest. Use them to leave notes, raise questions, and flag individual studies for a collaborator. Anyone in the nest can comment.

### Nest-Level And Study-Level Comments

Comments live at two levels. The difference is what the comment is attached to.

Nest-level comments are notes about the nest in general. Add them in the **Comments** panel on **Nest Home**. **Nest Home** also shows comments that mention you or your collaborators. Mentioned collaborators can open the study directly from the comment.

<figure><img src="https://305208404-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fxb7uNGATUgwQAjDVQRXG%2Fuploads%2FLQ0SDpHz5RvaxOmb08h3%2FScreenshot%202026-08-04%20at%2014.02.11.png?alt=media&amp;token=1f200136-925c-4b4f-ac2d-6e3e7134718a" alt="The Comments panel on Nest Home, showing a nest-level comment."><figcaption><p>Nest-level comments appear in the <strong>Comments</strong> panel on <strong>Nest Home</strong>.</p></figcaption></figure>

Study-level comments are attached to a specific study. They remain with that study, so anyone who opens it later sees the note in context. Add or view these comments anytime from a study's **Comments** panel at any stage of the review as well as in **Study Inspector**.

<figure><img src="https://305208404-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fxb7uNGATUgwQAjDVQRXG%2Fuploads%2FqbmCPnAROeLmOE5kLJZu%2FScreenshot%202026-08-04%20at%2014.03.53.png?alt=media&amp;token=e7298783-3cd9-4dba-90a1-aadc4ffd641c" alt="The Comments panel for an individual study, showing a study-level comment."><figcaption><p>Study-level comments stay with the study.</p></figcaption></figure>

### Mentioning A Collaborator

To mention a collaborator:

1. In the comment field, select **@**.
2. Select the collaborator.

Mentioning a collaborator sends them an email and marks the nest on the **Nests** page. Mention anyone who needs to review or act on a comment.

**Nest Home** offers two mention views: **Your Mentions** shows comments that tag you, and **All Mentions** shows comments that tag any collaborator.

### Resolving Comments

Resolvable comments help you track notes that need attention. They have an **unresolved** or **resolved** status. Unresolved comments stay visible, while resolved comments move out of the way.

When you write a comment, select the check-mark icon to mark it resolvable. Information-only notes usually don't need this status. A comment that mentions a collaborator is marked resolvable automatically. Turn this off when no action is needed.

<figure><img src="https://305208404-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fxb7uNGATUgwQAjDVQRXG%2Fuploads%2F1oChkQBbO2QiWiqvV19B%2FScreenshot%202026-08-04%20at%2014.08.24.png?alt=media&amp;token=cd30a5ee-b56e-4db8-9b27-35242751e373" alt="The comment field with the check-mark icon used to mark a comment as resolvable."><figcaption><p>Select the check-mark icon to mark a comment as resolvable.</p></figcaption></figure>

Anyone in the nest can change a resolvable comment between **unresolved** and **resolved**. This isn't restricted to the author. Comments created before this feature was introduced remain non-resolvable. They don't appear as open tasks.

Two places help you find open comments. On **Nest Home**, unresolved comments appear first. In [**Study Inspector**,](/review-workflow/study-inspector.md) use the **Comment Resolution Status** filter to find studies with resolved or unresolved comments.

<figure><img src="https://305208404-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fxb7uNGATUgwQAjDVQRXG%2Fuploads%2FeRmXuUG9VRVNTaJc6dL5%2FScreenshot%202026-08-04%20at%2014.10.44.png?alt=media&amp;token=8d607a9f-76ac-42f1-8a2f-e55a8487dcbc" alt="The Comments panel on Nest Home, showing unresolved comments first."><figcaption><p>Unresolved comments appear first on <strong>Nest Home</strong>.</p></figcaption></figure>

### Hide Comments

Comments can influence a reviewer's judgment. By default, a study shows every collaborator's comments.

To assess a study independently, switch its **Comments** panel to show only your comments. Other collaborators' comments remain hidden until you switch back.

<figure><img src="https://305208404-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fxb7uNGATUgwQAjDVQRXG%2Fuploads%2Ff0MN4xOXruDPRxdd5Dii%2FScreenshot%202026-08-04%20at%2014.11.52.png?alt=media&amp;token=878e9cb1-00e0-41f3-ba5f-d95d00aa88f3" alt="The Comments panel set to show only your comments."><figcaption><p>Show only your comments to assess a study independently.</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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.nested-knowledge.com/collaborate/comments.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.