Skip to Content
Technical walkthroughsReview a release (portal)

Review a release and record your decision

Review a release before it proceeds toward activation. Your decision becomes part of the release’s approval history.

Before you start

You need permission to record approval decisions in the release’s workspace. The release must be Review ready, and its creator cannot approve it. Recording an approval decision and activating a release are separate actions.

Review the release

  1. Select the correct workspace.
  2. Open Assure → Releases and select the release.
  3. Confirm the workload, release identifier, and current state.
  4. Open Bindings to review the asset versions included in the release.
  5. Review the relevant Evaluations, Policy, and other available evidence for your organization’s approval requirements.

Check that the evidence relates to the versions being reviewed. If required evidence is missing or unavailable, ask the release owner to resolve the gap before you approve.

A successful evaluation supports your decision within its tested scope. It does not establish that every possible behavior has been tested.

Record your decision

  1. Open Approvals.
  2. Select Record approval.
  3. Choose Approve or Reject.
  4. Review your selection, then select Record decision.

The decision is retained as an approval record. Check the approval history for your outcome, identity, and timestamp.

Recording an Approve decision does not itself activate the release. A separate authorized lifecycle action is required. Recording Reject records your decision; do not assume that it automatically changes the release’s lifecycle state.

Review execution evidence

For an execution-level investigation, open Assure → Evidence log and select the relevant record. Review the available policy decisions, sources, timing, and artifacts. Available fields depend on the execution and your access. Missing or redacted information is not evidence that an event did not occur.

Release proof-pack export is a separate, bounded workflow. It does not imply that every execution can be exported as a PDF or that a release pack contains all raw data. Ask the responsible operator for the approved export and its coverage limitations.

If you cannot record a decision

ProblemWhat to do
Record approval is unavailableCheck that the release is Review ready and that you have approval permission.
You created the releaseAsk another authorized reviewer to assess it.
The release’s state changed during reviewRefresh the page and check its state before continuing.
The decision could not be recordedRead the message and check approval history before submitting again.

Next

Return to release preparation or the task guides. Operators can consult the technical release evidence reference for export details.

For permission-scoped context-lineage API reads, consult the technical evidence reference.