Skip to main content
WriterzRoom turns governance obligations from each content passport into durable review work. Required reviews are routed after generation, assigned to qualified organization members, and visible at Reviews.
Approval decisions are recorded and synchronized to the content passport, but they do not currently block publication. Treat the queue as an auditable review workflow, not as a publication lock.

Qualifications and Permissions

Review qualifications describe subject-matter competency. Workspace roles describe product access. They are separate controls. An administrator does not automatically qualify for any governed review. Organization admins set qualifications under Workspace → Team after a member accepts the invitation.

Review Categories

Use the category selector in Reviews to focus the queue. Categories are qualifications, not workspace permissions, and one asset may require more than one category in sequential stages.

How Assignment Works

  1. The Quality Gate records required approvals in the asset’s content passport.
  2. The generation finalizer persists those obligations as review records.
  3. For each role, WriterzRoom selects an active organization member with the matching qualification.
  4. Selection is deterministic for the request-and-role pair, so retries do not move work unexpectedly.
  5. Reviews at the same stage can proceed in parallel; later stages wait until earlier required reviews are resolved.
If no qualified member exists, the obligation remains unassigned. Adding a qualification assigns matching pending work immediately. Removing a qualification revokes that member’s pending assignments and reroutes them when another eligible reviewer exists.

Review an Asset

1

Open Reviews

Open Review Queue under Review in the sidebar. The queue lists work you own and work assigned to you, with pending reviews shown by default and a count of what is assigned, overdue, and escalated above the list.
2

Inspect the record

Selecting a review opens it beside the queue. Anything unresolved before release, the decision controls, the routing reason, the release under review, and uploaded evidence sit next to the full asset, along with how many required gates have cleared.
3

Record a decision

Choose Approve, Request changes, Reject, or Waive. Required later-stage reviews remain locked until the current stage is resolved.
4

Request evidence when needed

A changes request can name the claim, source index, and missing substantiation so the next revision has an auditable checklist rather than only free-form feedback.

Review States

An open review says which of these it is in, rather than hiding the decision controls without explanation: If the release or the assignment changes after you open a review, the decision is not recorded. The page says so and offers Reload review so you decide on the current version.

Recovery and Escalation

An internal hourly sweep repairs missing or partial review routes, assigns unassigned work when qualified members become available, and marks overdue approvals for escalation. Immediate routing remains the normal path; the sweep is a recovery control. Every assignment — immediate or from the sweep — emails the reviewer, respecting their notification preference. It is not a webhook and does not fire on decisions, only on assignment.

API

All endpoints below use the standard API base URL and authenticated user API key.

Content Governance

Learn how review obligations are derived and recorded.

Workspace

Manage organization members and permissions.
Last modified on September 10, 2026