Human review

Human review sends a random sample of each project's automated moderation decisions to people you choose, who confirm each decision or change it. Set the sampling rates and work through the queue in Portal › Human review, and invite reviewers from Portal › Project members.

Sampling

Each project has two sampling percentages, from 0 to 100, which apply to new automated decisions:

Both start at 0, which samples nothing; 100 samples every eligible decision. Each asset joins the queue at most once, and sampling never delays or changes the automated decision: the asset is delivered according to its automated status until a reviewer changes it.

Reviewers need the content to judge it. When keepContentAfterProcessing is false, a sampled asset's content stays temporary until a reviewer decides it, and is then removed as usual. It is held for reviewers only, never delivered, and if nobody decides it within 14 days it is removed and the asset leaves the queue. These are never sampled:

• Automated purges, whose content is deleted as soon as they are decided.
• Assets under a safety hold.
• The parts extracted from documents and websites. A document or website itself is sampled when its parts first decide its status, if its content is kept after processing; otherwise its content was already removed by then.

If an asset's content is removed or the asset is deleted while it waits, it leaves the queue. See Asset lifecycle for content retention.

Anyone who can change the project's settings sets the rates: owners, administrators and members with custom permissions that include Change project settings (settings:write). Other people with access to the queue see it without the sampling settings.

Reviewers

Owners and administrators invite reviewers from Portal › Project members. A reviewer is a project member who sees only the human review queue and their own account: they have no access to the project's assets, folders, settings or API keys, and cannot download content. Reviewers can be promoted to editors or removed from the same page. See Members and permissions for invitations and other roles.

Owners and administrators can also work through the queue, as can members with custom permissions that include View reviews (reviews:read) to see it and Review content (reviews:write) to decide.

The queue presents the oldest pending asset first, one at a time. Reviewers read a sampled text document's text and view a preview image of other assets; when the content has since been placed under a hold, the preview is unavailable.

Decisions

A reviewer judges the asset's decision as it stands when they review it: the automated outcome, or the status someone gave the asset after it was sampled, which the queue shows. They confirm it by choosing the same status, or change it to another:

Changing the outcome requires a note of up to 1,000 characters; confirming accepts an optional one. Each pending asset takes one decision: if two reviewers decide it at the same time, only the first is saved.

• Confirming leaves the asset unchanged and appends the review to its classification.moderation.manualReviews with appliedToAsset: false.
• Overturning sets classification.moderation.status to the reviewer's decision and appends a manual review with appliedToAsset: true. As with any reviewer decision, it takes precedence over the automated one, while the policy assessment in classification.moderation keeps the automated result.
• Purging permanently deletes the stored content after an explicit confirmation, and no later decision can restore it. It is available only to people who can also delete assets, such as owners and administrators, never to reviewers, and not for content under a copyright hold.

Blocking keeps the content, so a later review can restore delivery.

To record decisions made in your own moderation tools, such as reports from your users, call POST /assets/:assetId/decision instead. It applies to any asset, sampled or not. A sampled asset stays in the queue, which then shows the status your app set.

The reviewed list shows each decision with its reviewer and whether it confirmed or overturned the decision it reviewed, together with how many decisions were overturned. Decisions stay with the project when a reviewer leaves or deletes their account; deleting an asset deletes its review decisions too.

Events

Confirming a decision emits no event, since the asset is unchanged. Seeing asset.review-requested, or subscribing a connector to it, needs reviews:read; a connector can use it to tell your team when new work arrives. See events for every fact.

Human review and policies

Your moderation policy makes every automated decision, and human review checks a sample of them afterwards. Reviewers judge individual assets; their decisions do not change the policy or how later assets are moderated. When reviewers keep overturning the same kind of decision, adjust the policy and test the draft against those examples.