Aug 2026 - Appeal Automation, Multi-Review QA, and NCMEC Previews

​

Appeals

• Appeal Received workflow: Publish the built-in Appeal Received workflow to enrich an incoming appeal, set its priority, and route it to the right queue before a reviewer ever sees it. The editor labels the appealer as its own target, so it is clear which party each action applies to. Receive and automate appeals
• Workflow-managed intake: POST /api/v2/appeals/ files the appeal against the original decision and runs that workflow. Existing appeal endpoints are unchanged. Learn more about sending data to Cinder
• Communications addressed to the appealer: On appeal workflows, Send Comms can address the person who filed the appeal, extending the reporter targeting already available on report and decision workflows.

​

Quality Assurance

• Multi-review on QA queues: QA admins can turn on multi-review for a QA queue so several graders score the same sampled decision independently. When graders agree, Cinder finalizes one grade as the trusted accuracy signal; when they disagree, the job escalates to a senior grader. A Multi-Review Results view shows each grader’s answers side by side with the resolution. How to configure multi-review
• Appeals tab in QA navigation: The QA appeals worklist, with filters for queue, analyst, appealer, and outcome, is now reachable from its own Appeals tab instead of only by drilling in from a dashboard panel.
• Appeal a grade from a closed decision: Reviewers can start a grade appeal from the actions menu on a closed decision, alongside the existing entry points in QA results and the QA decisions table.

​

NCMEC Reporting

• Preview reports before submitting: With the report preview setting enabled on a queue, choosing Submit opens a side panel showing the reports that decision would generate, section by section, before anything is sent. The job stays visible behind the panel. Workflows that fan out preview up to five related reports and show the total count.
• Complete missing fields at review time: Reviewers can fill in or correct a defined set of report fields in the preview, including incident details, reported-person and file metadata, and IP capture values. Those edits are applied to the report that is actually submitted.
• See where NCMEC is configured: A Usage tab in NCMEC settings lists the forms your mappings reference, the queues where those forms are enabled, and the workflows with a Send to NCMEC node, and links directly to each one.
• Credential checks that explain themselves: Cinder validates NCMEC credentials when you save them, and the connection status check now tells you whether credentials are invalid or NCMEC itself is unavailable.
• Richer IP capture events: Map port, event name, and possible proxy attributes on reported-person and file IP capture events, alongside IP address and timestamp.

​

Queue Management

• Select every job that matches your filters: On the jobs table, filter, then select every matching job across queues rather than just the current page, and apply one bulk action to as many as 10,000 jobs at once. Which actions are offered still depends on your roles and each queue’s settings.
• Escalation reasons you can act on: When a reviewer gives a reason for escalating a job, that reason is recorded on the escalation. It appears in job activity and the job actions table, can be filtered, and is included in the job actioned export. Queues can require a reason before a reviewer is allowed to escalate.
• Faster self-assignment: Your own account is pinned to the top of the assignment picker.

​

Review and Decisions

• Cancelled jobs are unmistakable: A cancelled job now shows a clear banner and alert in review, so reviewers do not spend time on a job that no longer needs a decision.

​

Workflows

• Conditions on reported attributes: On decision-created workflows, branch on the attributes a report actually flagged, so automation can treat a reported field differently from the rest of the entity.
• Jump to a node from the execution path: While testing, click a step in the execution path to focus that node on the canvas. Test workflows

​

Analytics and Exports

• QA accuracy by correct policy: QA decision charts break accuracy down by the policies that should have been applied. These correct policy dimensions replace the older policy dimensions on that data source, and existing QA charts were migrated to them.
• Group by a reviewer’s current identity: A Decision Made By (Current) dimension resolves reviewers by their current email, so reporting stays consistent when accounts change. On QA decisions, a matching dimension does the same for the original moderator being graded. Build analytics dashboards

​

Administration

• Policy viewer role: A new Policy viewer role controls read-only access to the Policies module. Existing teams received it automatically, so current access is unchanged; assign it to new teams that should be able to read policies without editing them. Role permissions reference

​

Webhooks and APIs

• Handle time and resolution time: Job actioned webhooks now include how long the job was held after assignment, and decision created webhooks include both that handle time and the total time from job creation to decision. Each field is omitted when there was no assignment or no recorded resolution time. Job actioned webhook Decision created webhook
• Clearer override lineage: Override decisions carry the originating job from the overridden decision’s chain, so downstream systems can tie an override back to the review it corrects. Decision created webhook