Skip to main content

Review & Decide

Some results can't be settled automatically. They queue up in one shared place, where an admin confirms or dismisses each one and the decision is recorded.

Who it's for: Admins who resolve flagged results and need the decision on record

Availability: Available

What you get​

  • One shared queue for every result that needs a person to decide, rather than per-worker hunting
  • An explicit Confirm or Dismiss on each item, so nothing sits in an ambiguous state
  • Visibility across the team — every admin sees every open task
  • Each resolution written to the audit trail, so you can show who decided what, and when

Turn it on​

→ Understand your Compliance Overview — how results reach the queue, and what to do with each one.

How it works​

Most checks come back with an outcome Oho can apply on its own. A few — ban-register matches and attachment reviews among them — need a person to look and decide. Those land in the shared Review & Decide queue at the top of the left menu instead of quietly changing a worker's status, and the queue is where the decision is made and recorded.

→ Understand your Compliance Overview — the dashboard these items are flagged from → Ban Checks — one of the result types that needs a decision → Core Entities — what each outcome means

For developers

Resolutions change a verifiable's outcome, so subscribe to the verification events rather than trying to read the queue.

→ Webhooks & event delivery

Good to know​

  • The queue is shared, not assigned — every admin sees every open task, so agree between yourselves who works it.
  • Every resolution is written to the audit trail. Treat a dismissal as a decision you'd be comfortable explaining later.
  • Where an item needs a document or a detail you don't hold, ask the worker for it with a fetch request rather than dismissing it.