Why did someone miss my comment?

Use an @mention when a specific person needs to act. A general comment may be visible without creating the same direct notification.

Should changed requirements live in a comment?

Discuss the change in comments, then update the brief with the accepted direction so nobody has to reconstruct it from the thread.

Can I edit or remove a comment?

Use the available comment menu when the action is permitted. If the comment changed a requirement, also update the brief so removing or editing the discussion does not erase the accepted direction.

Comments, mentions, and reactions

Add feedback

Use comments for decisions, questions, and review notes that belong to the request. Reply to continue a specific thread and use reactions for quick acknowledgement.

Mention someone

Type @ in supported editors to mention a teammate or the PIWOT℗ team. Mentions create a clearer notification than a general comment.

Edit or remove a comment

You can edit or delete your own comments. Workspace access determines whether additional moderation controls are available.

Write feedback that can be acted on

Name the object, explain the change, and add the reason. Replace vague comments such as make it pop with direction tied to hierarchy, audience, brand, or the decision the asset must support. Group related feedback before sending it when possible.

Use mentions for ownership

Mention a person when they need to answer, review, or decide. A general comment remains visible to request members but may not create the same direct notification. Do not mention everyone when one owner can resolve the question.

Preserve the final decision

Edit a comment only to correct or clarify your own message. If the team changes direction later, add a new comment so the sequence remains understandable, then update the brief with the current requirement.