Comments

Comments are short, dated, author-attributed notes attached directly to an object. They hold the back-and-forth that happens while work is in progress — a clarification, a question to the owner, an agreed next step — without touching the object’s formal fields, its status or its score. The formal record stays clean; the conversation stays next to it.

Where comments appear

A comment always belongs to exactly one object. The panel sits at the bottom of the detail page for:

Object	Where
Requirement assessment	The requirement detail page, and the respondent and auditee assessment views
Risk scenario	The scenario detail page and its edit form
Applied control	The control detail page
Finding	The finding detail page

The panel is collapsed by default and shows the comment count beside the Comments heading, so a busy thread never pushes the object’s own fields off the screen.

Posting and reading

Comments are ordered oldest first, so a thread reads top to bottom like a conversation. Write in the composer at the bottom and press Post, or use Ctrl+Enter. Each comment shows its author, its body and its age as relative time — “just now”, “5 minutes ago” — switching to a full date once it is old enough for that to matter.

Processed versus active

Every comment is active when posted. Once a point is settled, mark it processed; the control on the comment toggles between Mark as processed and Mark as active, so reopening is one click.

Processed comments never disappear — they stay in the history — but they can be folded away. When a thread contains any processed comments, a Hide processed / Show processed toggle appears in the panel header with a count, which is what keeps a long-running thread readable.

Editing and deleting

An author can edit their own comment. The first time the body actually changes, the comment is flagged edited, and that marker stays from then on — so a reader always knows the wording they are looking at is not the wording other participants originally saw. Deleting is available to the author and to an administrator.

Action	Who can do it
Post a comment	Anyone with comment access in the object’s domain
Edit a comment	The author only
Delete a comment	The author, or an administrator

Respondents and auditees can post, edit and delete their own comments on the objects assigned to them, so the discussion works in both directions rather than being an internal-only channel.

Tip

Use comments for the conversation and the object’s own fields for the conclusion. A decision that only exists in a comment thread is a decision an auditor will not find — once a thread settles something, write it into the observation, the justification or the status, then mark the thread processed.

Turning comments off

Comments are enabled by default across the platform. An administrator can disable them instance-wide from Extra → Settings → Feature flags, which removes the panel from every object. See Feature flags.

Related

• Audits — where requirement-assessment comments appear.
• Applied controls — discussion on the action plan.
• Risk assessments — discussion on scenarios.