BlueprintPage 54
54EXPERIENCE
Admin Console & Security UX
Make the authority graph and decision history more important than vanity charts.
- Priority
- P0
- Phase
- MVP
- Primary owner
- Product Design
- Status
- Blueprint
Objective
The console should be optimized for investigation and control rather than marketing dashboards. Security users need fast navigation from risk → agent → authority → action → evidence → remediation.
What to build
- Home: agent inventory, critical risks, violations, approvals, incidents and spend.
- Agent profile: identity, owner, authority graph, tools, policies, activity, risk and cost.
- Policy center: templates, simulation, versions and enforcement status.
- Investigations: timeline, evidence, related agents/resources and containment actions.
- Integrations: health, scopes, permissions and sync status.
Implementation decisions
- Use consistent risk language and avoid unexplained AI-generated conclusions.
- Make policy explanations accessible from every blocked/approved action.
- Support saved views and filters for teams.
- Provide keyboard-efficient workflows for SOC/IAM analysts.
Definition of done
- Analyst can reach evidence from an alert in a few clicks.
- Critical controls are not hidden behind decorative dashboards.
- Admin actions show impact and confirmation before execution.
Success metrics
- Analyst task completion time
- Alert-to-agent navigation time
- Admin error rate
- Daily active security users
UX PRINCIPLE
Make the authority graph and decision history more important than vanity charts.