Agentic platform
Reviewer queue
The Evidence Reviewer agent does most of the triage. The reviewer queue is what's left for you.
Most evidence syncs produce mostly the same passing rows over and over. Reviewing every one wastes time. Skipping review entirely is dangerous.
The reviewer queue is the middle path: the Evidence Reviewer agent auto-approves the recurring passing rows and isolates the rest — failing rows, anomalies, anything that changed materially since the last sync — for you to look at.
How auto-approval works
On each sync, every evidence row is given a review_status:
auto_approved— passing, recurring, matches the pattern of prior approved rows.needs_review— failing, anomalous, or first-time. Lands in the queue.approved— manually approved by a reviewer.rejected— manually rejected. Excluded from control scoring.
The recompute trigger that powers framework completion percentages filters by bothstatus (pass/fail) and review_status (approved/rejected). A passing row that hasn’t been reviewed yet doesn’t count.
Why this matters for audits
An auditor will ask “who approved this evidence?”. With the reviewer queue, every approved row has either an explicit user attestation or an auto-approval lineage tying it to a prior approved row that was manually attested.The queue
Open Evidence Vault → Reviewer Queue. The queue surfaces:
- New failing rows since the last review pass.
- Anomalous rows the Evidence Reviewer agent flagged for human eyes.
- Rows that changed materially (a passing row that started failing, or vice versa).
- Rows tagged with a sync that the Integration Health agent flagged as suspect.
Each queue item shows the row, the agent’s reasoning, and the prior state. You approve or reject inline. Rejection requires a one-line note that becomes part of the audit trail.
SLAs and reminders
Items left in the queue beyond a configurable SLA (default 7 days) trigger a daily email reminder to the assigned reviewer. Critical-severity items escalate sooner.
Bulk operations
For high-volume integrations, you can bulk-approve a filter (“all passing rows from this M365 sync”) with a single attestation. The system records the bulk operation as a single audit-trail entry referencing the row count and filter.
Pair with audit periods
The reviewer queue respects the active audit period. Rows tagged to past periods are immutable — they were attested at the time and aren’t re-surfaced.