> ## Documentation Index
> Fetch the complete documentation index at: https://docs.cortex-labs.ai/llms.txt
> Use this file to discover all available pages before exploring further.

# Request a review from Explorer or a workflow

> Submit an exact artefact version with explicit reviewers, passes and a clear dependent path.

Use this procedure when a saved output needs review. You need access to the subject and authority to submit it in the workspace.

## Prepare the exact subject

Open the intended artefact version. Check its content, assets, citations and rendered output. Save unfinished edits before choosing the review subject.

Identify the decision you need. Review of a report is different from an Explorer plan decision or an agent question.

## Submit from Explorer

1. Open the saved workspace artefact from the investigation.
2. Choose its review action and confirm the exact version.
3. Select the required passes and responsible people or teams.
4. State the review purpose, criteria and any known limitation.
5. Submit and inspect the resulting review item and assignment.

Keep the final required publication pass human. Agent checks can support that review but cannot replace it.

## Configure a workflow request

In the workflow, identify the step that produces the review subject. Configure its review gate and authorised assignees.

Connect outcomes deliberately. Only paths dependent on the review wait for its result; independent permitted work can continue.

Test approval, rejection and requested changes. Check that a rejected subject cannot reach the intended approval-only publication route through another edge.

An ordinary workflow question or Verdict form has its own wait semantics. It is not automatically a multi-pass output review. Name the intended review path in the configuration.

## Inspect the handoff

Open the review queue or app review element. Confirm requester, subject version, required passes, current assignee and any related run.

Queue placement grants no new subject access. A reviewer who cannot read the output or evidence needs the correct access route.

| Subsequent action | Result to inspect |
| - | - |
| Approve | Records approval of this exact version. Publication remains separate. |
| Reject | Returns the rejection to the requester or configured workflow path. |
| Request changes | Returns reasons for revision. A new subject version needs a new review. |
| Comment | Supplies advice without approval. |

Changing the subject supersedes earlier applicable passes. Reassignment or changed required passes can invalidate pending actions. Preserve earlier decisions as history.

Continue with [Decide an assigned review](/vantage/review-and-publish/decide-review) or [Publish or withdraw an approved artefact](/vantage/review-and-publish/publish-withdraw).


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.