Introduction to Policy
Choose a Policy learning path and prepare accounts, catalogs, and example inputs.
Start with one policy, a known scope, and a clear review responsibility.
This path separates preparing a draft from approving and delivering it.
Scope means the data locations or runtime consumer that the exercise should affect.
Data and artificial intelligence (AI) exercises use different inputs and verification evidence.
Choose a Responsibility
Choose the path for your responsibility:
- Authors prepare authoring capabilities and applicable policy access.
Follow your first policy.
- Reviewers and approvers obtain the capability for their decision.
Follow lifecycle and governance.
- Platform operators obtain cluster and dependency access.
Follow Installation.
- Application developers obtain a gateway token and the configured application programming interface (API) base.
Follow the worked API lifecycle.
These are responsibilities, not additional product roles.
Refer to roles and permissions
before requesting access.
Complete a First Workflow
Follow these steps to get started:
- Prepare access and example inputs.
You have an identified author, reviewer, scope, and verification owner.
- Refer to states and revisions.
You can distinguish saved work, governed content, and delivery evidence.
- Follow the first-policy journey.
You save, submit, and review a draft before checking its target-specific delivery.
After approval, follow delivery verification.
Verify the target-specific result instead of treating approval as protection.
For permission or validation failures, use Troubleshoot.
1 - Prepare Access and Example Inputs
Prepare separate user accounts, supported catalog inputs, and verification responsibilities before authoring.
Prepare this checklist before creating a tutorial policy.
Use a nonproduction scope that your team permits you to change.
Do not use the example to test protection against production data.
Identify the exact data locations or runtime consumer before choosing policy inputs.
Before You Begin
Complete these prerequisites:
- Obtain the Policy address from your platform operator.
- Identify whether the exercise uses Data or artificial intelligence (AI) authoring.
- Read roles and permissions.
- Confirm the target integrations required by your release and exercise.
Prepare the Exercise
Prepare the exercise with the people who will perform it:
- Sign in with the account that will author the policy.
The account can open Policy and perform its assigned authoring operations.
- Ask the platform administrator to verify the required command capabilities.
The author can create work and edit policies they own or can access.
- Identify the reviewer and approver for this exercise.
Each person uses their own account with the appropriate decision capabilities.
- Select an available classification from your environment.
For a Data exercise, confirm it resolves to the intended discovered locations.
- Select the intended principals from the configured catalog.
You can explain who should receive each permission.
A principal is a runtime subject, such as a directory group, not a Policy reviewer.
- Confirm the supported protection method or AI permission choices.
Your inputs match the authoring lane and target release.
- Agree who will verify delivery and protection after approval.
That person has the necessary target access and diagnostic permissions.
If catalogs are empty, stop and ask an operator to check discovery and integration setup.
Do not fabricate classification identifiers or select unrelated production locations.
If authoring access fails, resolve the permission problem before saving work.
The following values illustrate an exercise, not preinstalled catalog objects.
Replace them with real values selected from your environment.
The table lists example exercise inputs and what to verify before using each one:
| Exercise Input | Example | Verify Before Continuing |
|---|
| Policy name | Customer email exercise | Choose a name your team can identify and later archive. |
| Classification | A classification containing email addresses | Confirm the selected classification actually resolves to your exercise scope. |
| Principal | A test application group from the catalog | Confirm membership and intended permission with the identity owner. |
| Author | Alex | Use Alex’s own authenticated authoring account. |
| Reviewer | Morgan | Use Morgan’s separate account with review and approval capabilities. |
| Verification scope | One known nonproduction Data location or AI consumer | Record the intended target and who can inspect its protection or receipt evidence. |
Alex and Morgan are illustrative people, not account names to provision.
Do not share tokens or credentials to simulate a role handoff.
Verify Preparation
You can identify the selected scope, principals, method, and review owner.
You also know which delivery evidence will count as success.
Save these choices with your team’s exercise notes.
Do not record access tokens in those notes.
If a definition remains unclear, consult the glossary
before substituting an unrelated catalog value.
Continue with the Quickstart.
For installation work, start with Installation.