# Comments

> Leave a threaded comment on a step, a point on the canvas, or a region of it, and resolve it when the work is done.

Comments are threaded notes pinned to the canvas. Use them to ask why a step is built the way it is, flag something to a colleague, or leave yourself a note that survives closing the tab.

## Leaving one

Press `C` and click where the comment belongs. What you click decides what it is pinned to:

| Pin it to    | By                                       | Use it for                                                 |
| ------------ | ---------------------------------------- | ---------------------------------------------------------- |
| **A step**   | Clicking the step                        | A question about that step's configuration                 |
| **A point**  | Clicking empty canvas                    | A note about the area around it                            |
| **A region** | Dragging a box across part of the canvas | A remark about a branch or a group of steps taken together |

A pinned comment stays with what it is pinned to, so a step you move takes its comments along.

## The comments list

Open **Comments** from the **More (⋮)** menu to see every thread on this canvas rather than hunting for pins. Four controls shape the list:

| Control                 | What it does                                          |
| ----------------------- | ----------------------------------------------------- |
| **Show resolved**       | Includes threads somebody has closed. Off by default. |
| **Unread first**        | Puts threads with new replies at the top.             |
| **Only mine**           | Narrows to threads you started or replied to.         |
| **Show pins on canvas** | Hides the pins without closing the list.              |

`Shift+C` toggles the pins on their own, for a screenshot or a screen share where the canvas should read clean.

## Replying and resolving

Anyone in the workspace can reply to a thread. A thread is marked read for you once you have opened it, which is what **Unread first** sorts on.

**Resolve a thread when the work it asked for is done.** It leaves the default list and stays findable under **Show resolved**, so the reasoning is kept rather than deleted.

## Who can change what

| Action                     | Who                                          |
| -------------------------- | -------------------------------------------- |
| Reply                      | Anyone in the workspace                      |
| Edit a message             | Whoever wrote that message                   |
| Delete a message           | Whoever wrote that message                   |
| Resolve or delete a thread | Whoever started it, or a workspace **Admin** |

Editing is per message, not per thread: you can always correct your own reply, and never somebody else's.

## Examples to copy

**Ask about a step without breaking the flow.** Press `C`, click the step, and write the question. The next person to open the canvas sees the pin on the step it is about, rather than a message somewhere else describing which step you meant.

**Review a branch.** Drag a region across the branch and comment once on the whole thing. A point comment beside it would not say which steps you meant.

**Clear a canvas for a demo.** `Shift+C` hides every pin. The threads are still there afterwards.

## What's Next?

- See what else several people on one canvas can do at once in [Real-Time Editing](/build/the-canvas/real-time-editing).
- Find the rest of the canvas-wide controls in the [Utilities Menu](/build/the-canvas/canvas-utilities).