> For the complete documentation index, see [llms.txt](https://docs.smaq.io/documentation/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.smaq.io/documentation/features/command-center.md).

# Command Center

The Command Center is SMAQ's at-a-glance triage view. Instead of clicking through five dashboards and three automations, you open one screen and see:

* What needs your attention right now (alerts firing, anomalies, pacing issues)
* Live snapshots of headline metrics across every platform
* In-flight media plans and their pacing status
* Open recommendations from Media Plan Intelligence, Creative Winner Detector, and other agents

> **\[Screenshot needed]** Command Center page with sections for Alerts (3 firing), Headline metrics strip (Spend / Conversions / ROAS today vs yesterday), Media Plans in flight (2 plans with pacing bars), and Recommendations from AI agents.

### Sections

#### Alerts firing

Every active [Metrics Alert](/documentation/features/automations/metrics-alert.md), [Multi-Metrics Alert](/documentation/features/automations/multi-metrics-alert.md), [Anomaly Digest](/documentation/features/automations/reference.md#anomaly-digest), [Budget Pacing Alert](/documentation/features/automations/reference.md#budget-pacing-alert), and similar alerting automation lands here when triggered. Click an alert to see the snapshot.

#### Headline metrics

A platform-aware strip showing today's headline metrics with comparison to yesterday and the prior 7-day average. Customizable per project — pick the metrics that matter to your business.

#### Media plans in flight

Every active [media plan](/documentation/features/media-plans.md) with:

* Days remaining
* % of budget consumed
* Pacing status (Ahead / On / Behind)
* Latest KPI vs target

Click into a plan to see full detail.

#### Open recommendations

Outputs from agentic automations that haven't been read yet. Includes:

* [Media Plan Intelligence](/documentation/features/media-plans/intelligence.md) recommendations
* Creative Winner Detector findings
* Search Term Analysis recommendations

Mark recommendations as read or dismissed as you action them.

### When to use Command Center

* **First thing in the morning** — your daily situational awareness.
* **Before a weekly review** — pulls the headline numbers you need.
* **When you've been away for a few days** — catches you up faster than reading every automation email.

### When NOT to use it

* For deep analysis. Use a [dashboard](/documentation/features/dashboard.md) or [chat](/documentation/features/chat.md) for that.
* For ad-hoc reporting. Use [Reports](/documentation/features/reports.md).
* For first-time setup. Build datablocks and dashboards first; Command Center pulls from those.

### Permissions

* Available to Owner, Editor, Member, and Viewer roles. Chat User doesn't see Command Center.
* Public dashboards don't expose Command Center — it's a project-internal view.

### Tier availability

* **All tiers** — Command Center is included starting at Starter.

### Tips

* **Customize the headline metrics strip.** Defaults are sensible but generic. A B2B SaaS plan probably wants MQLs and demo bookings, not blended ROAS.
* **Resolve alerts.** Don't let them pile up. The triage value of Command Center degrades when you have 12 firing alerts you haven't acted on.

### Related

* [Automations overview](/documentation/features/automations.md) — alerts feed Command Center.
* [Media Plans overview](/documentation/features/media-plans.md) — plans feed Command Center.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://docs.smaq.io/documentation/features/command-center.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.