What it does

Shows every pending human checkpoint in your workspace — anything a workflow paused on, waiting for someone to approve or reject it.

Why you should use it

This is where you actually control what MAEL is allowed to do unsupervised. Nothing that reaches this queue proceeds without your explicit decision.

Where to find it

Two places, same underlying data:
  • Sidebar → Approvals — every pending approval at every level (content, technical, publishing, billing, or anything flagged “dangerous”)
  • Sidebar → ContentReview queue — the same list, narrowed to just content

What information you must enter

An optional text comment per decision — see below.

Step-by-step

1

Open Approvals (or the Review queue)

Cards are listed newest-first, each showing what’s being requested and the artifact itself.[SCREENSHOT NEEDED: Approvals page with multiple pending cards]
2

Read the artifact

For content, the draft or its evaluation summary is shown right in the card.
3

(Optional) Add a comment

Saved permanently to the audit trail.
4

Click Approve or Reject

The card disappears from your queue the moment you decide.

What happens after you click Approve/Reject

  • Approve → the paused workflow resumes and continues (e.g. toward publishing).
  • Reject → that path stops. MAEL does not automatically retry — a person decides what happens next.

How long-running items are shown

Approvals aren’t “running” — they’re paused, waiting. If a SLA deadline was set, its badge turns red once overdue, but nothing times out or auto-decides on its own.

How to understand the output

See Understand Your Results for how to read the scores shown alongside a content approval.

What to do based on the output

Full guidance: Take Action.

Common mistakes

  • Approving without reading the artifact — see the warning in Take Action.
  • Expecting a rejected item to reappear automatically after being fixed — it won’t; whoever owns that content needs to explicitly restart the relevant workflow.

Troubleshooting

Queue says “All clear” but you expected something to be there → check whether the item actually failed the automatic quality gate instead (status review_required) — those don’t appear in the approval queue until someone investigates why first. See Understand Your Results.