Posts

Posts are the project’s conversation, on the project’s Posts page and right on its Overview. A post is text — up to 5 attached files if you need them — and anyone whose role includes Posts can write one.

There is no edit, so read a post back before you send it with the arrow button. A post can be deleted — see below — but not changed once it’s up.

Threads and mentions

Reply on a post starts its thread; replies all sit one level under the first post, so replying to a reply joins the same thread. New posts and replies notify the project’s team, with the people in a thread told specifically when it gets a reply — and to be sure a particular person sees something, @-mention them, which notifies them even if they are not on the project.

Posts and your client

A post goes to your team unless you say otherwise. The composer’s To: Team control, shown only if your role includes the Client portal permission, switches to To: Client; the field and the send button turn green so it’s obvious where the post is headed, and sending puts it on the client’s portal and notifies them by email — there’s no extra confirmation, and a post sent in error can be deleted. It stays on To: Client for your next post until you switch it back. While it says To: Client, the project’s client users join the @-mention list; on a team post they aren’t offered, because a mention the client can’t see would go nowhere.

Replies inherit the visibility of the thread they’re in: inside a client-visible thread the composer is already set to To: Client and sends straight to the client’s portal — there’s no choice to make. If your role doesn’t include Client portal, the Posts page tells you Your role does not include Client portal, so you can’t reply to this client-visible post.

In the feed, a client-visible post reads posted to the client instead of commented, with a small green eye on the author’s avatar and a green outline on the card. Attachments on them land in the project’s Client Portal folder, same as any portal post. You can also post as the client from the portal preview — it just isn’t the only way in.

On a completed project the conversation stays readable but closed — no new posts or replies.

Deleting a post

Hover over a post and open the ⋯ menu that appears beside it, then choose Delete — a confirmation follows. You can delete your own posts; admins can delete anyone’s; a client can delete their own from My Project. Deleting a top-level post takes its whole thread with it, and the modal tells you how many replies will go. Deleting a client-visible post also needs the Client portal permission — if the client can already see it, you need the grant to change it. Attachments go with the post, and posts on a completed project can’t be deleted.