Policy Lifecycle and Governance on

Submit Saved Work for Review

Mon, 01 Jan 0001 00:00:00 +0000

Act as the author who has prepared and saved proposed policy work.

Before You Begin

Complete these prerequisites before submitting work:

Save and inspect the proposed work.
Confirm policy:edit and applicable owner/editor access through capabilities and grants.
Identify the reviewer who will receive the policy identifier.

Submit Current Work

To submit the current saved work, follow these steps:

Open the saved policy in Policy Library.
Inspect its current draft content and validation findings.
Correct hard failures before continuing.
Select Submit for Review when Policy offers the action.
Supply reasoning and acknowledge only the current, permitted reviewable conflicts when prompted.
Confirm In Review in current policy detail. Submission changes the saved draft’s review status. It does not publish the policy.
Give the policy identifier to the separately authenticated reviewer.

Use a specific handoff message, such as: “Review this policy’s current submission, classification scope, and principal permissions.” Do not send credentials or ask the reviewer to reuse your browser session.

Review and Decide on a Submission

Mon, 01 Jan 0001 00:00:00 +0000

Authenticate as the reviewer, using your own account.

Before You Begin

Complete these prerequisites before reviewing a submission:

Obtain the submitted policy identifier from the author.
Confirm policy:review to inspect saved validation and request changes.
Confirm policy:approve if you will approve the submission.

An owner/editor grant does not supply either capability. Refer to authority requirements.

Inspect the Current Submission

To inspect the submitted policy, follow these steps:

Open the policy identifier that the author handed off.
Confirm that the current draft remains In Review.
Inspect classifications, principals, methods, and permissions.
Inspect the current validation findings.
Read permitted history and the author’s review reasoning.

For direct application programming interface (API) use, read policy detail and GET /policies/{policy_id}/validation under your reviewer identity. Saved validation returns the exact current head and its Draft-ETag. The head is the latest saved snapshot in the proposal. The entity tag (ETag) is a concurrency validator, not approval evidence. Use that current token for the decision. Do not reuse the author’s pre-submission token.

Correct Returned Work and Resubmit

Mon, 01 Jan 0001 00:00:00 +0000

Act as the author after a reviewer requests changes. Use your own authenticated account with edit capability and policy resource access. The returned proposal remains editable, even when the interface labels it Rejected. An existing governed revision remains unchanged. Returned work is not yet a new submission. Save records corrections. Resubmission returns those corrections to In Review.

Before You Begin

Complete these prerequisites before correcting returned work:

Obtain the policy identifier and correction request from the reviewer.
Confirm edit capability and applicable owner/editor access.
Keep the existing proposal. Do not create a replacement policy.

Correct the Proposal

To correct the returned proposal, follow these steps:

Restore Policy Intent or Retire a Policy

Mon, 01 Jan 0001 00:00:00 +0000

Policy rollback and archive solve different problems. Rollback proposes earlier policy intent for another review. Archive removes this policy’s configuration from the receiving products. Neither operation restores a database or rolls back a software installation. Restoring database contents is an operator recovery task, not a policy rollback. Closing a draft abandons only proposed changes. It does not withdraw approved output.

Refer to history and states and revisions first.

Before You Begin

Complete these prerequisites before restoring or archiving a policy: