Feedback loses value the moment it detaches from the work — a screenshot in an email, "the second one" in a chat. Comments in Bloom stay pinned to the reference or board they're about, so the discussion and the thing it discusses never drift apart.
How comments work
Comments attach to references and to boards, and each comment starts a thread:
- @mentions — pull a teammate into the discussion; they're notified directly.
- Emoji reactions — acknowledge without adding noise to the thread.
- Resolve / unresolve — mark a thread handled once it's addressed. Resolved threads get out of the way but aren't lost; reopen one if the point comes back.
Comments vs notes
The two are easy to conflate, but they do different jobs:
- Notes are flat text annotations you attach to a reference — context, sourcing, intent. They're statements, not conversations.
- Comments are threaded discussions — questions, feedback, decisions, with @mentions and reactions.
The distinction matters most when presenting: whether viewers see your notes is a per-link setting (never, on hover, or always), covered in viewer permissions.
Notifications
When someone comments on your work or @mentions you, you're notified two ways:
- In-app — in your Bloom notifications.
- Email — on by default, with a toggle in your account notification settings if you'd rather keep it in-app only.
Comments from presentation viewers
Comments aren't limited to your workspace. If a presentation link has Comment enabled, viewers can leave comments without a Bloom account. They can identify themselves with a name first, so feedback from a multi-person review stays attributable. Client comments land on the referenced work just like a teammate's, and you can carry the thread from there.
Good to know: encourage clients to comment on specific references rather than sending a summary afterward. Feedback anchored to the work is feedback you don't have to decode.