Comments & feedback

Comments live on an artifact and remember the version they were left on. Your team comments in the app; client contacts comment through their share link; AI tools read and answer with list_comments, add_comment and resolve_comment.

Who sees what

Comment	Visible to
Internal note	Your team only. Never shown to clients — replies included.
Team comment on an artifact filed under a client	Your team and that client’s contacts on their share links.
Client comment	Your team and the client’s contacts.

Contacts only ever see threads addressed to their own client.

Threads, mentions and change requests

Reply to any comment to keep the discussion in one thread.
@mention teammates to put the comment in their inbox.
Mark a comment as a change request when it asks for something to change. Change requests reach the team’s inbox as such and stay open until resolved.
Resolve a thread when it’s dealt with, optionally noting the version that made the change (“resolved in v4”).

Pinned comments

Comments can point at an exact spot in the report, so the next version can change precisely that.

HTML and Markdown — pin to selected text (the quote is kept), an element, or a point. The viewport width is recorded too.
PDF — pin to a point on a page or to selected text. Positions are stored per page as fractions of the page, so they stay put at any zoom level.

Pins show up in the viewer for both your team and clients, and in list_comments as the CSS selector or the PDF page and position.

Client approval

On a published version, a contact with comment access can:

Approve the version, or
Request changes, with an optional note. A note opens a change-request thread, tracked and resolved like any other.

Either way your team is told in the inbox. A client’s decision never changes the artifact’s status — your team decides what happens next.