124
Active users with role-based access
Administrative Control
Control the platform without burying governance in back-end configuration.
The admin settings surface is now route-native in `apps/web`, making platform control and policy stewardship visible, governed, and easier to audit.
6
AI policy bundles in force
3
Admin changes pending approval
93%
Services with named owner and notification rule
Administrative Domains
Each configuration area should have an owner, review cadence, and audit trace.
| Domain | What It Controls | Owner | Review Pattern |
|---|---|---|---|
| Users and roles | Audience visibility, admin rights, service-owner permissions, approver scopes | Platform admin | Monthly access review |
| AI policy and routing | Eligible tiers, blocked actions, approved sources, escalation rules | IT leadership + governance | Quarterly policy review |
| Knowledge governance | Published source sets, owner approval, confidence thresholds, review dates | Knowledge owner | 30-day source review |
| Notifications and escalation | Stakeholder updates, bridge notifications, approver nudges, vendor alerts | Service desk lead | Monthly service test |
| Service ownership | Catalog ownership, dependency accountability, budget and reporting responsibility | IT manager | Quarterly service review |