Inspect and Use the Policy Library

Use the Library to inspect saved Data and artificial intelligence (AI) policies. The Library includes policies created in Policy and information imported from Policy Integration Manager (PIM). Authored policies have Policy identifiers and governance history. Native identifiers belong to resources in downstream systems. Matching names do not make those identities interchangeable. Not every visible row permits editing.

Before You Begin

Complete these prerequisites before using the Library:

• Obtain the Policy address and your own authorized account through access preparation.
• Confirm policy:audit before inspecting restricted operations.
• Arrange an authorized operator’s help if you lack that capability.

Access Policy Library

To open Policy Library, follow these steps:

1. Log in using your own authorized account.
2. Open Policy Library.
3. Confirm that the list loads without a retrieval error.

A read-only account can inspect permitted information without acquiring mutation authority. If loading fails, keep the visible error instead of interpreting an empty list as no policies.

Understand Policy Library Columns

Read policy identity, source, classifications, principals, methods, exceptions, and modification information together. Scope means the selected classifications, applicable data, and principals covered by the policy. Treat policy state and protection state independently. An Approved row can still have an open draft or incomplete publication. The governed revision records approved intent. An open draft proposes changes to it. Refer to states and revisions.

An unavailable or stale validation count does not mean zero exceptions. Inspect the saved findings before submission or approval. Imported display-only policies do not become editable merely because you can view them.

Search for Policies

To find and verify a policy, follow these steps:

1. Enter a recognizable name, classification, or principal in the search field.
2. Inspect the matching rows.
3. Confirm the policy identifier or detailed scope before taking action.

Search narrows the displayed collection. It does not grant access. If no row matches, clear search and any active tile filter. Do not create a duplicate until you have checked the intended policy identifier.

Search Input Options

Use policy names, classifications, or principals as search input. Check the resulting scope before taking a lifecycle action.

Narrow and Sort the Policy List

To filter and sort the displayed policies, follow these steps:

1. Select the applicable Data Policy, AI Policy, or Drafts tile.
2. Choose an available sortable column to order the displayed results.
3. Clear the active tile when you need the broader collection again.

Sort Options

Use the sort direction shown by the selected column. Do not infer a review priority from list order alone.

KPI Tiles

Key performance indicator (KPI) tiles summarize the loaded collection. Open an individual policy to check publication and protection status. The tiles count policies, not completed deliveries.

Review Policy Summary in the View Panel

To inspect a policy summary, follow these steps:

1. Select the intended row or its View action.
2. Inspect the policy summary.
3. Confirm classifications, principal scope, protection methods, and outstanding exceptions.
4. Inspect the current governed and proposed information when available.

Do not mistake draft content for the governed revision. If details fail to load, reopen or refresh the policy before making a decision. Use the application programming interface (API) when the Panel does not expose required evidence.

View Panel Fields

Inspect identity, scope, current state, exceptions, and source together. Use current detail rather than inferring content from a summary cell.

Inspect History

To inspect a policy’s lifecycle history, follow these steps:

1. Open the policy’s view panel.
2. Inspect Change History.
3. Identify creation, saves, submission, review decisions, and approval events.
4. Check the responsible actor and timestamp for each relevant event.

Distinguish the currently approved version from earlier approved versions and the editable draft. Use the history view’s continuation control when more entries remain. Read the version’s actor, timestamp, and available notes before choosing it for rollback.

History lists lifecycle events and their metadata, not a full historical-content comparison. Repeated saves belong to one proposal and can appear as separate events. Each Save records a snapshot. The latest saved snapshot is the draft head. Keep current draft identity separate from governed revision identity. Do not treat a record version counter or saved snapshot identifier as a governed revision number. Do not infer that the first visible entry identifies the governed revision.

For complete permitted history, use GET /policies/{policy_id}/history. Follow pagination in the API reference instead of assuming the visible history contains every retained event. History can redact decision reasoning according to caller authority. An absent visible reason does not prove that the reviewer supplied none. An authorized auditor can use the separate audit export contract.

If history fails to load, do not treat the failure as an empty audit trail. Preserve the policy identifier and error for an authorized operator.

Inspect Lifecycle Operation Details

Use this task only with audit capability. Otherwise, give the policy identifier and visible error to your Policy administrator.

To inspect an operation when you have audit capability, follow these steps:

1. Open the policy’s Operations tab.
2. Select the latest request and read its attempt count and error message.
3. Copy its deployment identifier and support reference if you need help from your Policy administrator.

Restricted operation reads require audit capability. Read access does not confer retry or reconciliation authority. Continue with delivery issues.

Use Status-Aware Row Actions

Policy offers actions according to current state and authority. The server still authorizes each command. An absent action is not a reason to forge a request or broaden permissions.

Choose an available action that matches the work you need to do:

• Use edit or resume to prepare proposed work.
• Use submission to hand work to review.
• Use review for decisions.
• Use rollback or archive for restoration or retirement.
• Use close an open draft to abandon only proposed work.

Interpret Cedar Policy Source

Cedar source describes generated access rules. Use this reference when your view or API response includes Cedar source. It does not prescribe an additional Panel action. It does not show whether PIM applied the configuration or Guardrails retrieved it. Use delivery verification to check those results. For API authoring, keep the full structured compile request rather than replacing it with copied Cedar text.

Review Checklist

Compare the generated rules with the classifications, principals, and permissions you selected. If they differ, correct the structured authoring inputs and compile again.

Start Policy Creation From Policy Library

To start policy creation, follow these steps:

1. Choose Data Protection Policy or AI Policy.
2. Follow the selected authoring journey. Opening the form alone does not save a policy.

Refer to Data authoring or AI authoring. Treat Quantum Policy’s Coming Soon choice as unavailable.

Expected System Behavior

The selected journey opens an authoring form. Only a successful Save creates persisted draft work.