Skip to main content
WorkflowsCommunicationsQueuesReviewQANCMECAnalyticsWebhooks

Workflows

New actions and sharper conditions for report and appeal automation.
  • Change Priority: On report-received and appeal-received workflows, set the priority of the job the triggering report or appeal landed on, using a number from 0 to 99. On a report, that path also has to send the report to a queue, or there is no job to re-prioritize.
  • Close Related Jobs across multiple targets: Point one Close Related Jobs node at several entities at once, and use it on report-received workflows as well as the triggers that already supported it. The node warns when no queues or tags are selected.
  • Enforcement actions on Create Decision: Optionally record enforcement actions on the decision a workflow creates, instead of needing a second decision just to carry those actions. Enforcement actions
  • Reporter-scoped report counts: On a report-received workflow, a Reports Count condition can count only reports from the triggering reporter. That count leaves out the report that started the workflow.
  • Was not within last: Compare datetimes with a new condition operator for values older than a duration you choose.
  • Use provided media hashes: On hash-list classifier groups, match hashes already supplied on media attributes at ingest instead of always downloading and re-hashing, while still hashing media that has no provided hash.
  • Restore a previous workflow version: Open an earlier version in the editor as a draft, edit it, and save to create a new live version without changing the snapshot you restored from.
  • Decide which decision a communication belongs to: On Send Comms, choose the decision the message should attach to. When the workflow was started by a decision, that decision is the default. On a report-received workflow the default is empty unless you select a decision created earlier in the workflow.
  • Condition on the deciding workflow: On points-changed workflows, branch when a specific workflow applied the points.

Communications

Reusable wording for automated messages, managed in one place.
  • Templates library: Create named subject and message templates under User Communications, then pick a template on a Send Comms node and fill in its variables. Publish fails if that node leaves a template variable unfilled, or if the template it selected has been deleted.
  • Adopt wording from existing Send Comms nodes: The Templates page lists workflow nodes that still carry their own subject and message. Create template turns that wording into a shared template and points the node at it, unless the template asks for variables. In that case, fill those variables on the node in the workflow editor.
  • Webhook message format: Under User Communications, choose whether User Communication Created webhooks send the message as HTML, Markdown, or plain text. HTML stays the default. This control is turned on separately from templates.
To get started, contact your Cinder customer experience representative.

Queue Management

Find the right jobs faster, including work that is already resolved.
  • Filter resolved jobs in a queue: Expand the Status filter to Closed or Cancelled to browse resolved work in a queue’s jobs table. The default hides Closed and Cancelled, and it includes Paused.
  • Filter by related entity: On a queue’s entity-type jobs views, filter by relationship and related entity ID to focus on jobs connected to a specific entity.
  • Filter by media type: Queue and QA users can filter jobs, decisions, and reports by the media types on the job. Choosing a media type leaves out jobs whose media types have not been recorded yet, including jobs from before this shipped. Excluding a media type still includes those jobs.
  • Relationship Flagging per queue: Turn related-entity selection at decision time on or off for a queue. New queues start with it off; existing queues keep the previous on behavior. The setting applies only when the entity schema has Enable review on all related entities turned on. The toggle is not shown on QA or multi-review queues; those follow the original job’s queue. Queue settings
  • Uncheck jobs inside select-all: After selecting every job that matches your filters, clear individual rows before running a bulk action; those exclusions are respected for the action.
  • Job ID in custom links: Use the job ID token in schema custom links so review opens an external tool with the current job’s ID.

Review and Decisions

Clearer appeal context, safer policy application, and easier media inspection.
  • See the latest appeal override: When the appealed decision has since been overridden, reviewers see the latest override, with a warning, and can accept or adjust it before resolving the appeal.
  • Translate appeal and report reasoning: Translate Page now includes appealer and report reasoning alongside the entity text it already covered.
  • Confirm before applying policies: Applying policies from the apply-policy drawer asks for confirmation before the decisions are created.
  • Zoom images and PDF pages: In the media viewer, zoom job images and PDF pages from 1x to 5x. When a PDF has more than one page, jump to a page by number.
  • PDFs follow wellness tools: PDFs blur and grayscale with the same wellness controls as images, and links inside a PDF cannot be opened.

Quality Assurance

  • Sample by entity attributes: When a QA sampling configuration targets a single entity type, add attribute predicates so samples land on entities that match the attributes you care about.

NCMEC Reporting

  • Related report additional information: In an NCMEC template, map report additional information from a related entity, not only from the primary reported entity. This mapping is on NCMEC templates, not the older NCMEC workflow action.
To get started, contact your Cinder customer experience representative.

Analytics and Exports

  • Duplicate a dashboard: Copy an analytics dashboard, including its charts, as a starting point for a new one.
  • Share a dashboard with multiple groups: Grant dashboard visibility to more than one group at once. Build analytics dashboards
To get started, contact your Cinder customer experience representative.

Webhooks and APIs

Engineering teams can configure more of Cinder by API, and webhook payloads carry more lineage.
  • Manage webhook endpoints by API: List, create, read, update, and delete webhook endpoints through the API. Listing and reading require permission to view webhooks. Creating, updating, and deleting require permission to manage webhooks.
  • Queue, priority, and routing settings by API: Update queue settings through the API. Reading a queue returns its name, description, and job statistics, not the settings you wrote. Job priority preferences and job routing rules are read and replaced as a whole list. Escalation reasons can be listed, created, updated, and deleted.
  • Richer List Jobs filters: Filter jobs by category, assignment, tags, golden status, priority range, and created window in a single List Jobs request. Standard and appeal are the stable category values.
  • Event IDs on workflow calls: Sync workflow event calls return the event ID. Create-report responses include it only when the report is routed through workflows. The field is null when no workflow is listening for new reports, or when the request names a queue.
  • Policy target authors on decision webhooks: Decision created payloads include the authors on each policy target. Decision created webhook
  • Template slug on communication webhooks: When a reusable template produced a communication, the user communication created payload includes that template’s stable slug. User communication created webhook