Policy Use Cases

These use cases explain when to choose each workflow. Use the linked instructions for prerequisites, actions, and verification.

Use Case 1: Browse Policies in Policy Library

A stakeholder finds policies by name, classification, or principal. The Library tasks explain search and filtering. A read-only user cannot edit, approve, or archive policies.

Use Case 2: View Policy Summary Without Leaving the Library

A reviewer inspects scope, exceptions, and current state in the view panel. Refer to summary inspection. Do not confuse open proposed content with the governed revision.

Use Case 3: Start a New Policy From the Library

An author chooses Data or artificial intelligence (AI) authoring. Opening a form does not create persisted policy work.

Use Case 4: Author Policy Inputs Using Guided Steps

A Data author selects classified scope, principals, Encryption, and permissions. Scope means selected data categories, their applicable data, and the intended target identities. An AI author configures Federated Guardrails and principal-specific Unprotect permission. Save, preview, and submission remain different operations.

Use Case 5: Review Conflicts and Approve Policy

A separately authenticated reviewer inspects the current submission. The reviewer requests corrections or, with approval capability, approves reviewed work. Refer to review decisions and then delivery.

Use Case 6: Track Policy State Using KPI Summaries

A stakeholder uses key performance indicator (KPI) tiles to narrow the loaded list. The tiles do not establish target activation. Refer to detail and history for an individual policy.

Use Case 7: Change an Approved Policy Safely

An author opens replacement draft work while the existing governed revision remains current. The governed revision records approved intent. Saving a replacement does not approve it. The replacement follows submission and review. Automatic recompilation instead updates compiled output without rewriting author intent. Refer to automatic recompilation.

Use Case 8: Reject and Resubmit a Draft

A reviewer requests changes with an actionable reason. The author corrects and resubmits the same proposal. The Rejected presentation does not make the work permanently uneditable. Returned work awaits correction. Resubmitted work enters In Review for another decision.

Use Case 9: Roll Back to an Earlier Approved Version

An authorized author restores earlier policy intent as proposed work. Another review and approval must precede replacement of the governed revision. Policy rollback does not roll back software or restore a database.

Release Alignment Note

Choose an enabled authoring option. The guides below cover Data Encryption and Federated Guardrails. Options labeled Coming Soon do not start an authoring workflow.