Reviews

Reviews help teams make artefact changes explicit before they are used as baseline evidence. Reviewers approve the latest version of an artefact or request changes with a note. Approval state is tied to the version being reviewed, so later edits send the artefact back through review.

Open Reviews from the top workspace navigation, next to Inbox and My Issues.

Work through your queue

The Reviews page is a queue/detail workspace:

• The left rail lists artefacts waiting for your review.
• The right pane shows the selected artefact's review detail and version comparison.
• For me shows pending reviews assigned to you.
• Created shows the safe V1 subset of your pending reviews where you also created the latest version.
• Filter by module and sort the queue from the left rail actions.

When there are no reviews, the queue remains available and the empty state appears in the detail pane.

Review an artefact ViewerV

Select an artefact from the queue to inspect the changes since your last approved version or since creation. The detail pane includes the artefact identifier, module, current version, change details, traceability summary when available, and Version History.

Use Approve when the latest version is acceptable. Use Request Changes when the artefact needs work; rejection requires a note so the author has actionable feedback.

Access boundaries

Review queues are backed by the same source access rules as the Source Library. You only see review rows and detail data that your workspace and source permissions allow. Restricted or unavailable source and artefact details stay hidden rather than being exposed through the queue.

Baseline eligibility

Reviews affect baseline readiness. An artefact with assigned reviewers must be approved for the latest version before it can count as approved evidence. Editing an approved artefact creates a new latest version and makes previous approvals stale for baseline purposes.