Classifications, Principals, and Methods

Authoring combines the data or runtime scope with intended principals and permissions. Catalog choices have operational meaning. They are not interchangeable display labels.

Classifications and Scope

A classification identifies a category of discovered data. For Data protection, its resolved locations determine where protection applies. Review that scope before submission, particularly after catalog changes. The same display name does not prove the same current location set. Scope is the resolved set of locations or runtime subjects to which the selected inputs apply. Record identifiers and representative locations, not just a classification’s display name.

An empty selection and an unresolved classification are different problems. An empty selection supplies no classification. An unresolved classification supplies an identifier that current discovery cannot match to the required input. Correct the selected input when it is wrong. Ask an operator to inspect discovery when expected catalog data is missing.

Principals and Permissions

A principal identifies an intended runtime subject, such as a configured group. Select it from the available catalog and verify its intended membership. Do not confuse a policy’s runtime principals with the users administering Policy.

For example, an application group may receive an unprotect permission. That permission does not allow the group to approve Policy drafts. Conversely, approval authority does not automatically grant runtime data access.

Protection Methods and Authoring Lanes

Data authoring captures protection choices supported by the selected release and target. Artificial intelligence (AI) authoring uses its own principal-permission matrix. Do not infer that every method listed in a catalog supports both lanes. Do not treat hidden, unsupported, or unavailable choices as tutorial prerequisites.

Preview helps inspect target-specific output. Saving retains authored inputs, including supported incomplete work. Submission and approval require current validation and the appropriate review decisions.

Changing Context

Discovery, configured identities, and native target inventory can change over time. Policy therefore validates current context during governance operations. Automatic recompilation can also generate updated artifacts from approved intent. Neither mechanism authorizes silently changing an author’s proposed policy.

Continue with Data and AI authoring or validation and review decisions.