Work With Policies on

Create and Review Your First Policy

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

This journey uses two authenticated users: author Alex and reviewer Morgan. Morgan also needs approval authority to approve the corrected submission. Use separate accounts, not shared credentials or client-supplied actor names. This example does not require every deployment to enforce two-person approval.

Before You Begin

Complete these prerequisites before starting the example:

Complete access and example preparation.
Ask a Protegrity Provisioned Cluster (PPC) user with administrator permissions to assign Alex policy_author.
Ask that administrator to give Morgan the policy:review and policy:approve permissions.
Identify one discovered classification and one supported principal.
Identify the expected Data locations and their configured protection integration.
Use a nonproduction example that your organization permits you to protect.

Classification scope identifies the selected data categories and their applicable discovered locations. The selected principal is the target identity receiving permissions, not necessarily Alex or Morgan. Their Policy capabilities authorize authoring and review, not access to the protected data.

Common Policy Workflows

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

Use this map to choose the next task. Follow the linked instructions rather than maintaining separate copies of the workflow. For a complete worked example, use your first policy.

Policy Library Workflows

Start with Library inspection. Find the intended policy, inspect its current state, and read permitted history. Use the policy identifier to avoid acting on a similarly named row.

Policy Authoring Workflows

Choose Data authoring for the enabled Encryption journey. Choose artificial intelligence (AI) authoring for Federated Guardrails. Both paths require supported classifications, principals, and approved author access. Classifications select data categories. Principals identify the target identities receiving permissions. Neither path activates protection merely by saving a draft.

Policy Working Practices

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

Use these practices alongside the authoring and governance guides.

Policy Authoring Practices

Prefer explicit supported principals for a narrowly scoped first policy. Check classification identities and discovered scope rather than names alone. Scope includes selected classifications, applicable data, and intended principals. Review permission rows again after changing principal scope. Do not treat wildcard selection as a missing or empty scope.

Use a meaningful nonblank title. Inspect saved content and findings after Save. Do not interpret preview or an enabled Save button as submission eligibility. Refer to Data or artificial intelligence (AI) instructions.

Policy Use Cases

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

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.

Inspect and Use the Policy Library

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

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:

Policy Authoring Procedures

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

Policy offers separate Data and artificial intelligence (AI) authoring journeys. Use the lane that matches your protection target. These journeys share governance, but they use different permission models.

Before You Begin

Prepare discovered classifications, supported principals, and approved author access. Refer to start here and roles and permissions.

Configure Data Scope

Refer to Data scope selection. Scope identifies the selected classifications, applicable data, and intended principals. Select an available classification from the catalog rather than typing a new category name. Review changed scope before saving or resubmitting.

Policy Lifecycle Operations

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

Refer to lifecycle and governance for the complete actor handoff. Use the links below to choose the action you need.

Lifecycle States

Treat draft status, governed revision, and protection progress separately. The draft holds proposed changes. The governed revision records approved intent. Protection progress describes target-specific delivery or protection evidence, not draft readiness. An approved policy can have an open replacement draft. Refer to states and revisions.

Before You Begin

Check command capabilities and policy grants. An owner/editor grant alone never supplies review or approval capability.

Policy Integration Flows

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

Policy reads classifications, data locations, and principals from Traverse, and existing policy information from Policy Integration Manager (PIM). It uses those inputs to generate configuration for the receiving products.

Integration Architecture Summary

Traverse supplies discovery context and Data protection observations. PIM supplies existing policies, roles, and identity-source configuration. Federated Guardrails consumes the relevant published product output. Refer to concepts before choosing an authoring lane. Operators configure dependencies through operations.

Upstream Flow: Discovery Data Into Policy

Discovery identifies classifications and locations that affect policy compilation. Authors choose valid discovered scope rather than inventing location identities. Incomplete or unavailable discovery cannot establish complete protection evidence. Refer to Data authoring and Data verification.