Comments
A comment anchors to whatever it is about — a card, a group, an empty point on the canvas, the board as a whole, or a range of text inside a document. Comments thread, resolve, and support @ mentions that notify the person named. A comments toggle hides all of them when you want to see the board clean.
Comments attach to the thing they are about. This is the whole design: feedback that lives in a sidebar, ordered by time, loses the connection to what it referred to within a day.
What you can comment on
| Anchor | Reads as |
|---|---|
| A card | "this image" |
| A group | "this sequence" |
| An empty point | "something should go here" |
| The board | "the whole thing" |
| A text range in a document | "this sentence" |
Right-click → Comment, or the rail's + → Annotate → Comment.
Threads
Comments thread with replies. Resolve when the thing is dealt with — resolved comments are archived rather than deleted, so the record of why something changed survives.
Resolving and hiding a comment is for its author and for people who can edit the board; deleting one is for its author. Someone with view-only access sees those buttons on their own comments only.
Mentions
Type @ in a comment to mention someone. They are notified. See Notifications.
You can also mention clusters, documents and cards, which turns a comment into a navigable link rather than a description of where to look.
Hiding them
The comments toggle hides every comment bubble on the board — for you only, not for everyone. Use it when presenting or when the feedback has piled up and you want to see the work.
Bubbles on a crowded board
Comment bubbles lay themselves out to avoid covering the content they refer to and to avoid stacking on each other, so a heavily-reviewed board stays readable.
Who can comment
On the canvas, anyone who can open the board, including viewers. Editing a card is a different right from talking about it, and feedback is the point of sharing a board with someone. Public links are the exception: they are anonymous, and comments need an account.
A comment on a text range is different: it lives inside the document's text, so it follows edit access. A viewer can open a document's comment threads and read them, but adding, replying to, resolving or deleting one needs edit access.
From your own code, or an assistant
The Comments API lists a board's threads, the ones inside its documents included, and adds, resolves and deletes comments under the same rules. Connected over MCP, an assistant can read the feedback on a board, act on it, reply, resolve what it dealt with, and comment on the words of a document.
Comments versus votes
- A comment is a sentence: reasoning, a request, a decision, with a thread and a record.
- A vote is a count: which of these, quickly, with no discussion.
If you want to know why, use a comment.
Frequently asked questions
Can I comment on empty canvas?
Yes. A comment can anchor to a point rather than an object, which is how you leave "something should go here".
How do I hide comments for a presentation?
The comments toggle hides every comment bubble on the board. It affects only your view.
Do resolved comments disappear?
They are archived rather than deleted, so the record of a decision survives.
Machine-readable: /docs/collaborate/comments.md · /llms.txt
What changed and when: /changelog