Skip to content

Commenting on work

Leaving threaded comments on a note, a content item or a task, mentioning teammates, and the difference between an internal comment and one a client can read.

Updated

Comments are the internal conversation about one record: a note, a content item or a task. They are threaded, they can mention a teammate, and they can be resolved when the point is settled.

A comment is internal by default, which means only people with access to the workspace can read it. Marking one client-visible is a disclosure decision: an approval-link holder outside your organisation can read it. That is why it needs a higher permission than an internal comment does.

Comments always belong to one item. Opening the comments page without one gives you nothing to comment on, and it says so.

BEFORE YOU START

  • Access to the workspace to read and to write an internal comment.
  • The "create" or "edit" permission to write a client-visible comment.
  • A record to comment on. Reach the page from the note, content item or task itself rather than directly.

STEPS

  1. Open the record and follow its comments link, which carries the record type and id in the address.
  2. Read the thread. Replies are indented under what they answer.
  3. Write in the box at the bottom. Type @ to mention a teammate; they are notified.
  4. Tick "Also visible to the client" only if it is safe for an external reviewer to read.
  5. Choose Reply on a comment to answer it in place.
  6. Choose Resolve when a point is settled, or Reopen if it comes back.

WHAT YOU SHOULD SEE

The comment appearing at the end of the thread, marked internal or client, and anyone you mentioned receiving a notification.

WHAT THIS WILL NOT DO

  • It will not comment on nothing. "This page is not pointing at anything to comment on." means the link carried no record.
  • It will not approve or reject anything. A comment is a comment; decisions are made in approvals.
  • It will not email anyone. Mentions notify inside the product, and nothing in this product sends mail.
  • It will not let you resolve a thread on your phone. The mobile screen writes and replies; resolve and reopen are web only, and it has no mention autocomplete.

WORTH KNOWING

A mention is checked at the moment of notifying: if the person you named cannot reach the workspace, they are not told. A name that cannot be resolved is dropped rather than failing your comment.

IF IT DOES NOT WORK

  • "That record is not in this workspace." means the id in the address belongs elsewhere.
  • "create or edit permission required." is the refusal for making a comment client-visible. The same comment posted internally will go through.
  • "That comment could not be posted. Please try again." and "That thread could not be resolved." are the fallbacks.
  • "No comments yet." is the empty state.
  • On mobile, "We never heard back, so it is not known whether that comment was posted. Your text is kept - reload the thread and look before sending it again, or it could be posted twice." means exactly what it says. Check before resending.

COMMON QUESTIONS

Who can read a client-visible comment?

Anyone holding a review link for that item, in addition to your team. Treat it as external.

Do comments count towards approval?

No. An approval is recorded through the approvals flow and carries the version it was made against. Comments carry no decision.

  • Reviewing and deciding on content

    Working the approvals queue, what "edited since submitted" means for your decision, and the separation-of-duties rule that stops an author approving their own work.

  • Briefs and notes

    Writing strategy notes, campaign briefs and content pillars, how every save becomes a new immutable version, and what marking a note "client" actually means.

  • Tracking tasks

    Keeping a workspace's tasks on a board or in a table, working a checklist, and which task fields exist behind the API but have no control in the product.