Use policy workflow to change authority boundaries without losing control.
The policy workflow surface helps operators move a rule from draft to enforced state without skipping simulation, approval, or evidence capture.
Who this is for
Policy owners, security operators, and tenant admins managing authority boundaries and enforcement changes.
When to use it
Use this when policy must change because of a new adapter, a deny pattern, a budget update, or a governance control revision.
Required setup
Required setup: tenant connection in the console and a clear understanding of which scope or actor boundary is changing. High-risk changes may require approval before promotion.
How to use
1. Open policy workflow
Start at /console/policies/ and confirm the tenant context before editing or reviewing any rule.
2. Draft or load the policy
Create the new rule or open the existing one you need to modify. Keep scope, actor, approval, and budget boundaries explicit.
3. Validate structure
Run validation before simulation so you catch malformed or incomplete policy definitions early.
4. Simulate impact
Use simulation to see what decisions would change and which workflows would be affected if the rule became active.
5. Promote with evidence
Only move the policy forward when simulation results are acceptable and any required approvals are complete. Record the resulting evidence and version state.
What success looks like
Related console surfaces
/console/policies/ - policy workflow surface/docs/policies/ - policy reference