Configure Artificial Intelligence Protection

Configure artificial intelligence (AI) protection as an authorized policy author. Classification scope selects data categories. Principal scope selects the identities covered by generated rules. The target principal is not necessarily the authenticated Policy author.

Before You Begin

Complete these prerequisites before configuring an AI policy:

• Complete example preparation.
• Identify one classification and one explicit supported principal.
• Confirm that your operator has configured the intended Federated Guardrails consumer.

Choose Scope and Settings

To configure the AI policy scope and settings, follow these steps:

1. Open Policy Library.
2. Select AI Policy from the creation choices. Opening the form does not create a saved policy.
3. Select the prepared classification.
4. Select the supported principal.
5. Select Federated Guardrails.
6. Review the generated title.
7. Enter a clearer title when needed.

Use catalog identities for users, agents, services, or groups that your deployment supports. Do not substitute display names for native identities. Stop if a required classification or principal cannot load. Send the missing selection and error message to the Traverse integration administrator before submitting work.

Knowledge Graphs, Protegrity Semantic Guardrails, third-party guardrails, and Privacy appear as Coming Soon choices. This procedure does not enable those choices.

Set Unprotect Permission

Unprotect allows a selected principal to recover readable values from protected content. The generated rules also protect data for the selected principals. The Unprotect toggle controls the reverse operation. Turning it off does not disable protection.

To set permissions for each principal, follow these steps:

1. Inspect the principal row in Permissions Matrix.
2. Set Unprotect according to the principal’s intended permission. Enable it to allow readable values. Otherwise leave it off.
3. Review every row after changing the selected principals.

Bulk selection applies to the current principal selection. Use it only when every selected identity needs the same Unprotect decision. Inspect individual rows afterward.

An all-principals selection produces wildcard scope rather than a list of named identities. Use it only with explicit authorization for that broader scope. For a first policy, prefer an explicit principal.

Verify the Intended Matrix

Check the classification and every principal-specific Unprotect decision together. Changing principal scope can change generated rules. Do not infer saved or deployed permission from the matrix alone.

Next, inspect preview and save. After Save, follow governance and Guardrails delivery verification.