Skip to main content
Comments turn static pages into lightweight review spaces. Mentions pull the right people into the loop without forwarding threads in email. This article covers threading, @mentions, and how to stay sane when notification volume spikes.

​
Threads

Start a thread on a selection. Resolve threads when addressed so everyone can see what is still open versus done.

​
Best practices

Keep one topic per thread when you can—easier to resolve and easier for newcomers to scan. Quote or anchor to specific paragraphs so replies stay in context months later.

​
Permissions

Readers may or may not see comment sidebars depending on project policy. If someone says they cannot view a thread, check their project role and whether the page is in a restricted space.

​
Mentions

@mention teammates to pull them in. Mentions respect project membership: you cannot @mention someone who should not already access the underlying content.

​
Typing and suggestions

Most editors autocomplete @handles after a few characters. If a colleague recently joined, refresh the member list or wait for directory sync before assuming a name is missing.

​
Bots and integrations

Some integrations post as service accounts. Mentions to those accounts may open tickets or chat channels—confirm behavior in your automation settings.

​
Notifications

Mute noisy threads or adjust frequency in personal notification settings. Batch digests work well for deep work; real-time alerts suit on-call rotations or launch weeks.

​
Email vs in-app

If email feels loud, switch critical threads to in-app only and reserve email for @mentions directly to you. Mobile push can mirror desktop preferences or be disabled for weekends.