Comments & collaboration

Policy review happens in the Comments tab of a policy’s detail view. Comments are threaded, can be anchored to specific text, and can be resolved when an issue is settled.

Opening comments

From a policy’s detail view, click the Comments tab. The tab label shows a badge with the unresolved comment count.

Leaving a comment

Document-level (on the policy as a whole)

1. Click + New comment at the top of the Comments tab.
2. Type your comment. Markdown formatting is supported — bold, italic, lists, code, code blocks, and links.
3. Click Post.

Anchored to specific text

1. In the policy body, select a span of text.
2. Right-click the selection → Add comment (or use the floating ”💬” button that appears on selection).
3. A thread opens with that quoted passage at the top.
4. Type and post as usual.

Anchored comments remember:

• The revision ID the anchor was placed against
• The start/end character offsets
• The exact quoted text (so the comment can “rebase” if the surrounding body changes)

Replies

Click Reply under any top-level comment to add to the thread. Replies are displayed one level deep — even deeply-nested replies flatten visually, though the data model preserves the exact reply-to structure.

Comments are immutable after posting. There is no “edit” button. If you need to correct a comment, reply with the correction.

@mentioning a user

Type @ in a comment field and start typing a name or email. A dropdown will match users in your tenant. Select one and the handle becomes a linked mention.

Heads up: mentions do not currently send email notifications. Mentioned users will see the mention when they next view the policy, but there is no push notification or email delivery. This is on the roadmap.

Resolving a comment

When a thread is settled (decision made, rewording applied, question answered):

1. Click Resolve on the top-level comment.
2. The thread collapses and turns gray but stays visible.
3. The unresolved count on the Comments tab drops by one.

Toggle Show resolved to hide or show resolved threads.

Who can resolve:

• Admin and Policy Lead can resolve any thread.
• Policy Editor can resolve threads they started.
• User cannot comment and cannot resolve.

Resolving records who resolved it and when. The original comments remain readable.

Anchor drift

When the body of a policy changes, anchored comments try to stay attached to their original text:

• If the quoted text still appears somewhere in the new body, the anchor rebases to that new location.
• If the quoted text is gone, the comment is marked orphaned. It’s still visible in the thread and the quoted text is shown, but it no longer highlights a position in the body.

Orphaned comments are often the right place to close a thread — the content being discussed is no longer in the policy, so resolve the thread with a note about what changed.

Limits

• 8,000 character cap per comment. Longer than that, break it into multiple comments or a shared document.
• No file attachments. Comments are text-only. If you need to share an image or PDF, link to it.
• Comments aren’t included in policy CSV exports. They live only in the web UI. If you need to archive a review, screenshot or copy/paste the thread.

Etiquette

• Prefer anchored comments for specific wording issues and document-level comments for higher-level concerns.
• When you resolve, leave a one-liner saying what you changed — future readers see the thread in context.
• Don’t use comments as a to-do list. InPolicy tracks policy edits in revision history; comments are for discussion of those edits.