Create and Review Your First Policy

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.

Do not grant a broad administrator role merely to follow this example. Refer to authority requirements.

Steps

Follow these steps to complete the author-to-reviewer workflow:

1. As Alex, configure a Data policy. Select the prepared classification and explicit principal, then configure Encryption and the required permissions.
2. Save and inspect the draft. Record its policy identifier and confirm that the saved content matches your selections.
3. Submit the saved draft. Confirm In Review before handing the identifier to Morgan.
4. As Morgan, review and request changes. For this exercise, request a clearer policy title with a nonblank reason.
5. As Alex, correct and resubmit. Confirm the corrected title and current submitted snapshot: saved content and findings, also called the draft head.
6. As Morgan, approve the current submission. Approval creates a governed revision: the approved intent. It also queues publication.
7. Follow Data delivery verification. Verify the current deployment and every expected location independently.

For artificial intelligence (AI) protection, substitute AI configuration and AI preview and Save for the first two tasks. Finish with Guardrails evidence.

Verification

You have completed the authoring and governance journey when history shows Alex’s submission, Morgan’s requested changes, Alex’s resubmission, and Morgan’s approval. You have not completed delivery merely because approval succeeded.

Stop when validation blocks submission or approval. Correct the field named by the validation message and reload the validation results. For a connection or directory error, ask the administrator of the named integration to investigate. If publication fails, preserve the deployment identifier and support reference. Refer to delivery issues instead of repeatedly approving unchanged work.