Publish your four core policies before rollout
Unlock invites and training only after compliance, data protection, IT security, and operations policies are published.
Drafts do not unlock rollout
Each core category must be published, not just generated or awaiting approval, before team rollout unlocks.
Unlocked organizations stay unlocked
If coverage later drops, Quick Policy shows warnings but does not relock invited users or published rollout activity.
Summary
- Unlock invites and training only after compliance, data protection, IT security, and operations policies are published.
- Use this guide to complete the workflow with audit-ready evidence and ownership.
- If you hit a blocker, run troubleshooting first, then escalate with context.
Steps
1. Complete the core onboarding profile
Finish the operational context needed for publishable policy output before generating baseline drafts.
2. Cover the four required categories
Create or adapt one published policy for COMPLIANCE, DATA_PROTECTION, IT_SECURITY, and OPERATIONS.
3. Run approval and publish cleanly
Submit each draft through approval, clear any comments, and confirm the policy status changes to PUBLISHED.
4. Verify rollout unlock
Open Team or Training and confirm the rollout lock is removed before sending invites or assigning training.
Verification
- Organization readiness shows 4 of 4 core categories published.
- Team invitations are no longer blocked by the operational baseline gate.
- Training oversight is unlocked and ready for day-0 rollout.
Troubleshooting
Team or Training still says rollout is locked.
Check that each required category is published, not archived, and not duplicated under the same category.
A publish workflow completed but readiness did not update.
Refresh the dashboard and confirm the policy status is PUBLISHED. If it is still blocked, review the missing category badges shown in readiness.
We were already unlocked and later edited or archived a baseline policy.
Quick Policy keeps the organization unlocked, but you should restore coverage to remove warnings and keep your audit story clean.
Workflow screenshots
Was this article helpful?
Next article
Environment prerequisites and deployment readiness
Confirm required integrations, secrets, and operational dependencies before broad rollout.
Continue to next guideRelated articles
Confirm required integrations, secrets, and operational dependencies before broad rollout.
6 min read
Follow the commercial launch sequence: onboarding, publish the baseline, unlock rollout, invite staff, assign training, attach evidence, and export.
4 min read
Understand the two-stage onboarding model and the exact threshold for drafting unlock.
5 min read