Command Center
Use Command Center to prioritize cross-product signals, assistant recommendations, and operational actions.
What this menu is for
Command Center is the operational briefing layer. It collects important signals from Costs, Alerts, Guardrails, Optimizations, Billing, Integrations, Organization, Security, and Developers, then presents them as a prioritized action queue.
Use it when you need to decide what deserves attention first.
How it differs from Overview
Overview answers: is this workspace ready for the current plan?
Command Center answers: what should this team do next across the whole workspace?
It can surface data quality issues, alert noise, governance gaps, optimization opportunities, integration health, billing limits, security posture, and developer setup problems. The detail and actions still belong to their owning menus.
Lenses
Command Center works best when users think in lenses:
- Executive lens for health, spend posture, risk and next step.
- Finance lens for cost movement, allocation, reports, savings and budget exposure.
- Platform lens for ingestion, provider health, traces, alerts and operational reliability.
- Governance lens for budgets, caps, policies, approvals, exceptions and audit.
Recommended workflow
- Start with the priority brief.
- Open the highest-impact signal.
- Check the cited source and related menu.
- Apply the fix in the owning menu.
- Reopen Command Center to confirm the action queue changed.
Premium usage pattern
Use Command Center as the weekly operating review. Keep it projected during FinOps, platform or governance reviews, then assign owners directly from the action queue. The most mature teams treat the queue as the bridge between detection and accountability.
What to avoid
- Do not use Command Center as a replacement for audit logs.
- Do not treat every signal as equally urgent.
- Do not fix metadata, provider keys, policies or billing from the wrong menu. Follow the owning link.