Skip to main content
Every task has one comment thread. The most important thing on it is who can read each comment.

​
One thread, two audiences

A client writing in the portal lands in the same thread as your internal notes. Each comment carries its own audience: Client-facing comments are marked in the list with a Client can see this badge and a coloured rule down the left edge. An unmarked comment is always safe to treat as private.
Read the badge before you reply. Without it, a client’s question and an internal note look identical, so people answer the client in a comment the client can never see.

​
Post a comment

1

Open the task

Comments are on the full task page, under the Comments tab.
2

Write your comment

The box says “Write a comment. Use @ to mention a teammate.”
3

Choose the audience

Leave Send to client off for an internal note. Turn it on to address the client.
4

Click Post comment

The comment appears at the bottom of the thread with your name and the time.
The Send to client switch resets to off after every post, and whenever you open a different task. Sending to a client is always a deliberate act, never a setting you left on. Comments can be up to 5,000 characters. A blank comment is refused.

​
Mention someone

Type @ and start typing a name. A list of teammates appears; pick one and the handle is inserted. Mentions are highlighted in the posted comment. Each mentioned person gets a notification with a short preview of what you wrote. A member added to the roster without an email address cannot be reached by an @ handle from their address, because there is no inbox behind it. They can still be mentioned by their name handle.

​
Reply to a client

1

Turn on Send to client

The composer border changes and the placeholder becomes “Write a reply to the client.”
2

Check the warning

If the task is not shared with the client yet, a message appears: turn on Visible to client in More first.
3

Post

The comment lands in the thread carrying the Client can see this badge.
Marking a comment client-facing records your intent. Whether the client can actually read it depends on the task’s Visible to client setting and the project being shared with that client. Marking a reply on a not-yet-shared task is harmless – it becomes visible if and when the task is shared.

​
The Activity feed

The Activity tab beside Comments is a separate, read-only history: the task being created, stage moves, comments posted, attachments added and removed, due-date changes and estimate revisions with their notes. It is newest first and nothing on it can be edited or removed.

​
Example

Ruth Castillo, the Bluebird Coffee contact, writes in the portal on WR-142 Homepage wireframes: “Can we see a second layout direction?” Her comment appears in the internal thread with the Client can see this badge. Priya Raman replies with Send to client on: “Of course – Sarah will have a second direction with you by Thursday.” That reply carries the badge too. She then posts a second comment with the switch off: “@sarah this is a scope change, please flag the task as Additional billable.” Sarah gets a mention notification. Ruth never sees that one.

​
Options and settings

Comments are shown oldest first, each with the author’s avatar, name and the time it was posted.

​
Permissions

The client portal is a Pro feature. On the Free plan, the client half of the thread does not exist. See /concepts/plans-and-features.

​
What happens next

  • Each mentioned person is notified through the channels they have turned on. See /settings/notifications.
  • The task’s Activity feed records that a comment was posted.
  • A client-facing comment appears in the portal once the task is shared.
  • You are never notified about a comment you wrote yourself.

​
Common questions

Comments are part of the task’s record. There is no edit or delete control in the thread.
No. The thread is flat, in the order things were posted. Use @ to direct a comment at someone.
No. Notifications go to the people you mention. Mention the assignee if you need them to look.
Mentions resolve within your workspace roster. To reach a client, turn on Send to client and write the comment for them.
Yes. Comment bodies are shown as plain text, so tags and scripts are inert.

​
Troubleshooting

You do not hold task.edit in this workspace. Finance and Client roles cannot post internal comments.
The handle did not match a member of this workspace, or the person you mentioned has no email address on their record. Pick the person from the list rather than typing the handle by hand.
The task is not shared with the client yet. Open the full task page, go to More, and turn on Visible to client.
Three things all have to be true: the comment is marked client-facing, the task has Visible to client on, and the project is shared with that client. See /portal/what-clients-can-see.

What clients can see

The rules behind the portal firewall.

Portal comments

The client’s side of the thread.

Notification settings

Where mention notifications go.

Task details

Comments, Activity and Work log tabs.

Attachments

Files on the same task.