> ## Documentation Index > Fetch the complete documentation index at: https://docs.cinder.ai/llms.txt > Use this file to discover all available pages before exploring further. # Jul 2026 - QA Appeals, Bulk Overrides, and Workflow Filtering > QA grade appeals with dashboards, notifications, and exports, bulk decision overrides, Conditional Filter and Sampling workflow nodes, new QA decision filters, safer attachments, and bulk report creation ## Quality Assurance QA programs get an appeals process, and sharper ways to find the grades that matter. * **QA grade appeals**: A graded reviewer can appeal a grade on their own work from their profile QA results or the QA decisions table. Adjudicators accept or deny on the same grading surface that produced the grade, with the disputed grade, the original analyst, and the appeal reason all in view, and can escalate on queues where escalation is enabled. An accepted appeal corrects the accuracy score while the original grade stays in the decision chain for audit. Each grade can be appealed once. [Learn more about implementing QA](https://docs.cinder.ai/qa-implementation-guide) * **Appeal dashboards, notifications, and exports**: QA dashboards track appeal volume, acceptance rate, and outcomes, and the volume and outcome breakdowns drill into a filtered list of the appeals behind them. Graders are notified when an appeal is filed against a grade they made, and appeal outcomes are included in QA decision exports. * **New QA decision filters**: Filter QA decisions by violating status or by whether a form response was submitted, and read prediction confidence in its own column alongside grades. * **Sampling by entity type**: Target QA samples at specific entity types, and change the distribution method on a sampling configuration that is already running. [How to create a QA queue](https://docs.cinder.ai/qa/how-to-create-qa-queue) ## Workflows More precise targeting in the visual editor, and communications that carry real context. * **Conditional Filter node**: Narrow an array of related entities, or any upstream list, down to the items that match your rules, then point downstream actions at just those matches instead of the whole set. [How to act on a filtered set of entities](https://docs.cinder.ai/workflows/how-to-act-on-filtered-entities) * **Sampling node**: Route a percentage of traffic down a branch for gradual rollouts, holdouts, and spot checks. * **Extract JSON Fields supports lists**: Pull list values out of report metadata and other JSON attributes instead of single values only. * **Decision policies prefilled from the trigger**: Dropping a Create Decision action into a decision-created workflow prefills its policies from the triggering decision. * **External Classifier Scores on a related entity**: Point the External Classifier Scores node at a related entity, so scores supplied in the event payload create predictions on that entity instead of only the one that triggered the workflow. * **Reporter communications on decision workflows**: Send Comms can address the reporter on decision-created workflows, not only on report workflows. * **Event attributes in message bodies**: Communication templates can insert attributes from the entity the triggering event was about, separately from the recipient's own attributes. ## Review and Decisions Correct decisions at scale, and audit what your automation decided. * **Bulk decision overrides**: Select decisions in the decisions table, or every decision matching your filters, and override them in one action, available to queue admins, queue managers, and decision managers. Overrides run in the background, and decisions with an open appeal or an existing override are skipped. * **Filter decisions by originating workflow**: Filter the decisions table by the specific workflow that created a decision, across both legacy workflows and Workflows V2, making it much easier to audit what your automation decided. ## Queue Management * **Shift-click range selection**: In tables that support row selection, shift-click to select every row between your last selection and the row you clicked instead of ticking each one. ## NCMEC Reporting * **Report media from media list attributes**: Point a template at a media list attribute and Cinder uploads each image or video it holds as separate report media. * **Reported entity on media-less reports**: A report created from a workflow decision now shows that decision's entity even when the report carries no media. To get started, contact your Cinder customer experience representative. ## Security * **Safer note and case attachments**: Attachments must match an allowed file type on upload, downloads go through an authenticated endpoint, and new uploads stay unavailable until malware scanning clears them. ## APIs * **Bulk report creation**: `POST /api/v1/create_reports/` creates up to 100 reports in one transactional request instead of one call per report.