Comments and suggestions

Two ways to say something about a document without simply overwriting it: a comment, which is a note attached to some text, and a suggestion, which is a proposed edit someone accepts or rejects.

Comments

Select text and comment. The comment anchors to that text and travels with it as the document changes around it.

Reply to build a thread. Resolve when it is dealt with — resolved threads leave the margin but are not deleted, so the conversation is still there if someone asks why a paragraph reads the way it does.

Mention a colleague with @ to notify them. They get a notification with a link straight to the thread.

Suggestions

A suggestion is an edit shown as a tracked change: the new text underlined, the removed text struck through, both attributed. Nothing is applied until someone accepts.

This is the right mode when you want to fix the sentence rather than describe what is wrong with it. Reviewers who cannot edit directly — a commenter — can still suggest, so a subject-matter expert can correct a paragraph without being given write access.

Accept or reject individually, or accept everything at once from the review bar at the top of the document.

AI edits arrive the same way

When you ask Workover to revise a document, the result comes back as suggestions rather than replacing your text. You read the diff and decide. That is deliberate: an assistant rewriting a page in place is indistinguishable from losing your work.

The same applies to anything connected through the CLI or MCP — an agent proposes, a person accepts.

Publishing with unresolved suggestions

You cannot. The WP panel refuses while suggestions are outstanding, and says why: publishing would put the tracked changes, including text marked for removal, on your live site. Accept or reject them first.

Who can do what

Editors comment, suggest, and accept.
Commenters comment and suggest, but cannot accept.
Viewers read.

See roles and permissions.