> ## Documentation Index
> Fetch the complete documentation index at: https://docs.collivo.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Comments and AI-assisted review

> Attach feedback to exact content, ask agents to implement it, and use agents as reviewers.

export const SharedWithMe = () => <span style={{
  whiteSpace: "nowrap"
}}>
    <svg width="17" height="17" viewBox="0 0 24 24" fill="currentColor" fillOpacity="0.35" stroke="currentColor" strokeOpacity="0.7" strokeWidth="1.25" strokeLinecap="round" strokeLinejoin="round" style={{
  color: "#FE9A00",
  display: "inline-block",
  verticalAlign: "-0.2em",
  marginRight: "0.3em"
}} aria-hidden="true">
      <path d="M16 21v-2a4 4 0 0 0-4-4H6a4 4 0 0 0-4 4v2" />
      <path d="M16 3.128a4 4 0 0 1 0 7.744" />
      <path d="M22 21v-2a4 4 0 0 0-3-3.87" />
      <circle cx="9" cy="7" r="4" />
    </svg>
    <strong>Shared with me</strong>
  </span>;

export const SharedFolder = () => <span style={{
  whiteSpace: "nowrap"
}}>
    <svg width="17" height="17" viewBox="0 0 24 24" fill="currentColor" fillOpacity="0.35" stroke="currentColor" strokeOpacity="0.7" strokeWidth="1.25" strokeLinecap="round" strokeLinejoin="round" style={{
  color: "light-dark(#2E7D32, #4CAF50)",
  display: "inline-block",
  verticalAlign: "-0.2em",
  marginRight: "0.3em"
}} aria-hidden="true">
      <path d="M20 20a2 2 0 0 0 2-2V8a2 2 0 0 0-2-2h-7.9a2 2 0 0 1-1.69-.9L9.6 3.9A2 2 0 0 0 7.93 3H4a2 2 0 0 0-2 2v13a2 2 0 0 0 2 2Z" />
      <path d="M2 10h20" />
    </svg>
    <strong>Shared</strong>
  </span>;

export const PrivateFolder = () => <span style={{
  whiteSpace: "nowrap"
}}>
    <svg width="17" height="17" viewBox="0 0 24 24" fill="currentColor" fillOpacity="0.35" stroke="currentColor" strokeOpacity="0.7" strokeWidth="1.25" strokeLinecap="round" strokeLinejoin="round" style={{
  color: "inherit",
  display: "inline-block",
  verticalAlign: "-0.2em",
  marginRight: "0.3em"
}} aria-hidden="true">
      <path d="M20 20a2 2 0 0 0 2-2V8a2 2 0 0 0-2-2h-7.9a2 2 0 0 1-1.69-.9L9.6 3.9A2 2 0 0 0 7.93 3H4a2 2 0 0 0-2 2v13a2 2 0 0 0 2 2Z" />
      <path d="M2 10h20" />
    </svg>
    <strong>Private</strong>
  </span>;

## What this helps you do

Comments keep feedback connected to the part of an artifact being discussed. Use them to review work with colleagues, give revision instructions to an agent, or ask an agent to review an artifact and flag issues that need attention.

People who can see the artifact can participate in its comment threads. Their agents can also read and work with those comments when the artifact is available in the agent's context.

A common review cycle is:

`Agent drafts → a person comments → Resolve with AI → the agent revises → a person reviews → the thread is marked complete`

## Before you start

You need access to the artifact. Viewers can participate in comments, while changing the underlying content depends on their edit permissions.

Comments are shared with other people who can access the artifact. Do not use them for private notes or information that other permitted viewers should not see.

## Point to what you are commenting on

Comment placement changes to suit the artifact, allowing reviewers to point at the exact text, value, element, or region they mean.

| Content type | How comments are attached |
| - | - |
| Text documents | Selected words, lines, or paragraphs |
| Office files and PDFs | Selected text, a rectangular region on the page or slide, or a pin |
| Images, whiteboards, and other visual content | A pin placed on an element or visual region |
| Spreadsheets and other grid-based content | A selected cell or cell range |
| General artifact feedback | An unanchored comment on the artifact |

Anchored comments preserve useful context even when the discussion continues over several replies.

## Leave feedback on an artifact

### Text documents

1. Open the document.
2. Select the text you want to discuss.
3. Select **Comment** from the selection controls.
4. Enter the feedback and send it.

Collivo opens a comment popup at the selection so you can add the thread in place. The thread keeps the selected text with the comment. Open the comments panel from the document toolbar when you want to browse or manage existing feedback.

### Office files, PDFs, and visual content

For PDFs and Office files such as Word documents and PowerPoint presentations, choose the anchor that matches the feedback:

* **Text selection** — use when the feedback is about specific words, figures, or a sentence.
* **Rectangular selection** — use when the feedback is about a page or slide region, such as a chart, table, screenshot, or layout area.
* **Pin** — use when you want to point at a location without selecting text or drawing a region.

For images, whiteboards, and other visual content:

1. Select **Add comment** or **Add comment pin**.
2. Place the pin on the relevant image region, whiteboard element, page, or slide location.
3. Enter the feedback and send it.

A pin attached to a whiteboard element moves with that element. Pins and rectangular selections help reviewers identify the exact object, region, or layout area that needs attention.

### Spreadsheets and grids

Select the relevant cell or range before creating the comment. The thread records the sheet and cell selection so collaborators and agents can locate the value being discussed.

## Discuss and organize feedback

* Select a comment to reply in its thread.
* Type `@` in the comment box to reference a teammate or another available project item. Mentioning a teammate notifies them, as long as they can reach the artifact.
* Use the comment menu to edit or delete a comment when your permissions allow it.
* Filter the comments panel to show your threads, completed threads, or matching text.
* Mark a thread complete after its feedback has been addressed and reviewed.

A teammate can reach an artifact when it sits in the project's <SharedFolder /> folder, or when you have shared it with them from your <PrivateFolder /> folder — it then appears for them under <SharedWithMe />. If a mention does not reach someone, that is usually what is missing. See [Sharing and permissions](/sharing-and-security/sharing-permissions).

## Resolve feedback with AI

**Resolve with AI** sends a comment thread to the chat as referenced context so an agent can help implement the feedback.

1. Open the comment thread you want to address.
2. Select <Icon icon="sparkles" color="#1F7A5A" /> **Resolve with AI** in the reply area.
3. Review the comment reference added to the chat input.
4. Add any constraints or clarification the agent needs.
5. Send the request.
6. Review the resulting changes in the artifact.
7. Mark the thread complete when the feedback has been addressed satisfactorily.

<Tip>
  Add guidance such as “preserve the approved tone,” “do not change the figures,” or “ask before changing the structure” before sending the request.
</Tip>

Selecting **Resolve with AI** prepares the request; it does not send it automatically. You can review or expand the message first.

### Resolve several comments together

Use the checkboxes in the comments panel to select multiple visible threads, then select <Icon icon="sparkles" color="#1F7A5A" /> **Resolve with AI**. Collivo adds references for all selected threads to the chat input so the agent can consider the feedback together.

This is useful when several comments describe related changes, such as revising multiple sections of a proposal while keeping its terminology consistent.

<Note>
  **Resolve with AI** asks an agent to work on the feedback. **Mark complete** records that the discussion has been addressed. Always review the result before completing the thread.
</Note>

## Ask an agent to review your work

Where supported, agents can also participate as reviewers. Ask an agent to inspect an artifact and leave comments instead of immediately changing anything when you want to evaluate its findings first.

For example, an agent can:

* Flag unsupported claims or missing evidence in a report.
* Identify inconsistent figures or assumptions in a spreadsheet.
* Point out unclear visual hierarchy or missing content in a presentation.
* Review a whiteboard and comment on unresolved decisions or gaps.
* Highlight issues that require a person's judgment rather than silently choosing an answer.

For important work, consider using **Expert Panel** so multiple agents can review from different perspectives and synthesize their findings. This can make a draft more robust before peer review and reduce the amount of first-pass checking your teammates need to do.

Give the agent the source to check against, and say plainly that you want comments rather than edits. For example:

> Review this report against `Q3 figures.xlsx` and comment on any claim the data does not support. Leave comments only — do not edit the report.

Where supported, the agent can attach its comment to highlighted text, an artifact element, or another available anchor. Its comments appear in the same shared discussion so people can reply, make changes themselves, or send the feedback to another agent.

A useful pattern is:

`A person requests review → the agent leaves comments → the team evaluates the findings → a person or agent addresses them → the threads are completed`

## Expected result

Feedback stays attached to the content it concerns, people and agents can participate in the same review process, and completed threads provide a clear record of what has been addressed.

## Troubleshooting

* **You cannot find a comment:** open the comments panel, clear its filters, and search for text from the thread.
* **A text-linked comment no longer jumps to the right place:** the document may have changed. Use the quoted text in the comment to locate the updated section.
* **A visual pin points to an older version:** open the version where the comment was created or place a new comment on the current content.
* **Resolve with AI is unavailable:** confirm that you can participate in the thread and that chat is available in the project.
* **The agent misunderstood the feedback:** reopen the thread, add the missing constraint to the prepared chat message, and ask the agent to explain its intended change before applying it.
* **A mention does not find someone:** confirm that the person belongs to the organization, is a member of the project, and can access the artifact.

## Related articles

* [Manage notifications](/collaborate/notifications)
* [Work together in real time](/collaborate/real-time-artifacts)
* [Reviews and approvals](/collaborate/reviews-approvals)
* [Sharing and permissions](/sharing-and-security/sharing-permissions)


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.