1. Structure
1
Organizations & projects
Create production organizations and projects separate from PoC ones. Confirm each project’s type (Desktop Agent or API) matches its channel — it’s fixed at creation — and that your per-type project quotas are set within the system allowance.
2
Roles
Grant the least-privilege role each member needs.
2. Policies
2
Test with real cases
Send representative inputs and confirm PASS/MASK/BLOCK are correct (check Opticon).
3
Apply versions
Ensure each Guardian is pointed at the intended policy version — see Version & apply.
3. Integration
- API projects — issue per-environment API keys (named by caller), and make sure your app handles
MASK(useprocessed_content) andBLOCK, plus errors. - Desktop Agent projects — finalize Control Profiles and make sure the right ones are assigned to the production project, choose your Network Fail-Safe, set the Exit Password and confirm the Company Access Key in Desktop Agent settings, then roll out to Agent Users.
4. Operations
1
Monitoring
Confirm traces flow into Opticon, decide who watches them, and set the trace retention that fits your data-lifecycle requirements.
2
Quotas
Set project and Agent User limits for production scale.
3
Emergency plan
Make sure an Owner is available to reach the Kill Switch — only Owners can toggle it.
4
Audit
Confirm governance changes are captured in the Audit Log.
You’re production-ready when policies are tested and versioned, credentials are scoped, monitoring is live, and your team knows the emergency procedure.