CMS Operator Experience

Planned / Not Yet Implemented

CMS Operator Experience will replace default Payload starter-style non-admin pages with intentional operator landing and navigation surfaces.

Keep /admin as the primary Payload workspace for collections, globals, and schema-driven operations.
Make the CMS root page a lightweight operator landing page.
Put troubleshooting/governance surfaces behind explicit operator entry points.
Name the intended audience for every non-admin CMS route.
Enforce server-side authorization for browser-reachable CMS data. UI hiding is not a security boundary.
Revisit landing/navigation separately for cms-customer and cms-leverage after the split settles.

Canonical spec, stories, and acceptance tests exist.
The landing-page and non-admin route IA implementation is not complete.
Whitelabel/brand application waits for the governance-owned brand settings feature.