Configuration Control Center
ADMINISTRATOR
The Configuration screen is where workspace readiness is assessed and every operational setting lives. It reports the state of the workspace; it does not act on it.
The configuration control center. Check results, counts, and timestamps shown are point-in-time examples.
Pilot readiness
A controlled pilot is ready only when every required check passes. Readiness is evaluated across campaign grounding, generation configuration, eligible stories, stored content snapshots, and publication posture.
Readiness check states
| State | Meaning | Action |
|---|---|---|
| Pass | The requirement is satisfied | None |
| Warning | The requirement is partially satisfied and will limit output | Resolve before relying on the affected area |
| Blocked | The requirement is not satisfied | Must be resolved before activation |
Each check reports the specific condition it evaluated and where to fix it. Resolve blocked checks first, then warnings, then re-run the check.
Readiness reporting performs no generation, approval, scheduling, or publishing. Re-running the checks is always safe.
Why blocked and warning conditions matter
A blocked check means a downstream step will fail or produce ungoverned output — an unresolved backfill failure, a campaign without grounding, or a generation configuration that is incomplete. A warning usually means the work will proceed but on a smaller or less reliable basis, such as only part of the eligible stories having a stored content snapshot.
Treat the numbers on this screen as a snapshot of the moment the check ran, not as permanent values.
Configuration areas
The remaining tabs are documented separately:
- Content Generation
- Accounts
- Buffer Destinations
- Buffer Execution Log
- Media Storage
- Publication Safety
- Brand, Products, and Audiences
Was this helpful?
Last updated 1 month ago