Reviewers & approvals
Work with Human in the Loop approvals as a team: assign reviewers, use the Reviews portal, and process batch approval queues.
Overview
Draft & Goal supports human approval steps inside workflows via the Human in the Loop node. Reviewers pause a run, check content, then approve or reject before the workflow continues.
This page covers the team side: roles, the Reviews portal, and assigning colleagues. For node fields (approval mode, scoring, reminders), see Human in the Loop.
Who can review?
| Path | Who |
|---|---|
| Reviewer org role | Dedicated approval surface at /reviews (+ profile). No Builder/Runner Studio access |
| Assigned reviewers | Any eligible org member (active, signed in) selected on the HITL node — including Admins, Builders, and Runners |
Assign people who own the decision (editors, legal, account managers). Use the Reviewer role when someone only needs to approve and should not edit workflows.
Assign reviewers on a workflow
- Add a Human in the Loop node (Tools → Flow Control)
- Open node settings
- Select one or more Reviewers from your organization (required)
- Write a clear Message to reviewer
- Choose the approval mode (Any of / All of, etc.)
Eligible reviewers come from your organization’s member directory. If the list is empty, invite or activate users in Members & invitations.
A Human in the Loop step always needs at least one reviewer. Without assignees, the pause cannot notify anyone.
Reviews portal
Users with the Reviewer role work primarily in Reviews (/reviews):
- Queue of runs and batches waiting for their decision
- Filter by workflow when many Apps are in production
- Open a review to read the content and approve or reject
Builders and Admins who are assigned as reviewers are notified (email + review page) the same way; they do not need the Reviewer org role unless you want to restrict their Studio access.
Batch reviews
When Human in the Loop runs inside a Loop, each iteration can create a separate review request. Reviews are grouped on a batch review page so one person can process many items efficiently.
Track batch progress also from App → Run history → Batches. See Run history.
Tips for team operations
- Place HITL before irreversible actions (send email, publish to CMS, write to CRM)
- Prefer All of when legal or compliance must sign off; Any of when one editor is enough
- Keep the Reviewer role for external or part-time approvers who should not see the Builder
- Document who owns each approval step in the workflow description