Running Activate
The client mirror
See exactly what the client sees in Activate, read the operator diagnostics, and understand what you cannot change from it.
The client mirror
The mirror at /admin/activate/mirror/{engagement} shows the client's Activate portal as they see it, inside Command Centre chrome. It uses the same pages and tabs: Momentum, Briefs, Webinars, Events, Social, Stories, Partners, Revenue, Reviews and Strategy & setup.
The header
- {Org} · client portal, with a subtitle covering industry, latest Review number, whether Review data is ready, the AI enrichment state and readiness.
- A pulsing Read-only mirror pill.
- ← Command Centre returns to the summary.
Below that, the Integrations bar shows each provider's state and webhook health. An Inputs pill shows "No monthly refresh recorded", "Monthly reconciliation not complete" or "Monthly reconciliation complete". Manage integrations → opens the Integrations settings view.
Operator diagnostics
A collapsible section at the bottom. It holds health badges and attention chips:
| Chip | Raised when |
|---|---|
| {Provider} needs reconnecting | A connection is in Error or Revoked |
| {Provider} webhooks failing / disabled | Webhook delivery is degraded |
| Strategy baseline not captured | A live engagement has no baseline |
| N Review actions open | Recommendations from the latest Review are unactioned |
| No monthly refresh / Monthly reconciliation not complete | Monthly inputs are missing or older than 14 days |
| No metric snapshot | No snapshot computed yet |
The last three only fire for live engagements.
What you cannot do here
The mirror is a view. Client-owned actions are hidden or disabled: creating briefs, saving revenue, approving assets, resolving partner reconciliation issues, marking Review actions and editing settings. The reconciliation page says "The Command Centre mirror is read-only. Open the client portal to resolve, ignore, or retry an issue." The one staff-only action is Retry handoff on a brief whose setup handoff failed.
You cannot open the client's own portal as them. /portal/activate always loads the signed-in user's own engagement.