Now with AI-powered page building via MCP Server

Comments and tasks

Review a page where the page is. Comments anchor to a block, mentions reach people, and a remark that needs doing becomes a task with an owner.

Review usually happens somewhere else - a chat thread, a document, a spreadsheet of remarks - and then somebody has to carry each remark back to the thing it was about. Comments and tasks live on the page instead, and can point at a single block, so nobody has to describe which part they meant.

Comments

A comment belongs to a page, and optionally to one block within it. Anchored to a block, it shows as a pin on the canvas; anchored to the page, it sits in the panel with no pin. Replies thread under the comment they answer.

What a comment carries:

  • Up to 5000 characters of body.
  • Mentions of workspace members, which is what turns a remark into someone's problem rather than a note nobody reads.
  • A status of open or resolved. Resolving records who did it and when, so "was this dealt with?" has an answer that is not somebody's memory.

Who gets told

Mentioning someone sends them an in-app notification and an email carrying the page name and a snippet of what you wrote. Clicking the notification opens the page at that comment rather than at the top.

Replying also notifies the author of the comment you replied to - unless you are that author, or you already mentioned them in the reply. Two pings for one message is how people learn to ignore notifications, so it does not send them.

Tasks

A comment says what is wrong. A task says who will fix it and by when. Tasks anchor the same way - to a page, optionally to a block - and carry:

  • A title up to 200 characters, and an optional description up to 5000.
  • An assignee, who is notified when the task lands on them.
  • A status: to do, in progress or done. Changing it notifies the people who care.
  • An optional due date.

Every task assigned to you, across the workspace, is available in one list - so a person who edits ten pages does not have to open ten pages to find out what is waiting for them.

Permissions

Reading comments and tasks needs pages:view on that page, not on the workspace in general - a role scoped to some pages cannot read the discussion on the rest. Writing, resolving, assigning and deleting need pages:edit.

This matters when you invite a reviewer. A reviewer who may only view pages can read the thread but cannot answer it. If you want their opinion in writing, they need edit rights on the pages you want reviewed.

Where this does not reach

Comments and tasks are an editorial surface: the admin app and the GraphQL API. They are not part of the delivery API, so nothing here is ever served to your site's readers, and they are not exposed as MCP tools - an agent can write your content, but it cannot leave you a comment about it.

Next steps