Documentation

Renamed & rebuilt as Dashboard Branding. This page is kept only as a pointer — the standalone white_label toggle it used to document no longer exists. See dashboard-branding.md for the canonical, up-to-date feature behaviour.

• Feature key. The old white_label registry entry is gone; the current flag is dashboard_branding in Features::all() (default: true, available: true, member-gated).
• From a boolean toggle to a three-mode radio. The old on/off branding.white_label toggle became a tri-state mode stored in the branding.admin_logo_mode Setting and resolved by AdminLogo::mode() → webprocms (platform brand — also the forced value for non-members), site (the client's site logo + brand colors), or designer (the agency's own logo + swatches, Super-only uploads). Logo and chrome colors move together per mode.
• branding.white_label is legacy-only. It survives solely as a one-way migration fallback read inside AdminLogo::mode(); nothing writes it anymore.
• Dashboard chrome color is still driven by the --color-cms-primary token family (+ 19 shades) emitted by BrandingStyleService::dashboardStyleBlock(), with WEBPROCMS_DASHBOARD_PRIMARY = '#495092' as the platform default — all documented in Dashboard Branding, which also covers the designer swatches and the transactional-email chrome.

For the full feature — the three modes, the color model, who-can-do-what, and feature gating — read Dashboard Branding.