As Reviewer, assess investigation policy cases and releases where the connected Automation workflow is available. You can read permitted runs and cases, but Reviewer authority does not grant source datasets automatically or authorise operational source changes.
Establish the evidence boundary
Open the relevant saved investigation and check exact source, generation, namespace and code. Read declared coverage, captured relationship types, missing sequences, restrictions, corrections and traversal limits. A plausible graph is insufficient if the source never declared the relationships needed for the question.
Review independently
On Automation policies, use Open in Automation for the intended policy or candidate when offered. Check independent examples, complete native proof, exact query bounds, grouping, coverage decisions and full contributor list.
Case and whole-release reviews each require an eligible Reviewer independent of the relevant contributors, with recent authentication. A contributor cannot activate through LotTrail to bypass that exclusion. Current dataset grants, review validity, source dependencies and the expected active assignment are rechecked.
An activation does not itself investigate new evidence, send a message, print or change a source product. Existing saved runs retain their original source cuts and policy identity.
Keep native identity review separate
A local same-identity link is a Supervisor decision with supporting evidence and explicit dataset rights. It is not granted by the Reviewer role for policy approval. Likewise, source imports, cases and physical containment belong to their own responsible roles and products.
If the shared workspace is not connected, do not claim a local release button exists. Ask the responsible Author or administrator to arrange the supported review path. Continue read-only review of permitted saved evidence.
Use policies and review, coverage limits and identity links.