Brand Settings

Planned / Not Yet Implemented

Whitelabel brand settings are deferred until product accepts the settings model, fallback defaults, permission model, and ownership boundary.

CMS likely becomes the operator surface for brand settings.
Web and CMS should consume one canonical brand settings contract where feasible.
Minimum settings should cover logo or wordmark, primary/accent color or theme tokens, application title, favicon, and document metadata.
Later settings may include email branding, customer support links, and login/onboarding brand treatment.
Default brand values must remain deterministic so app chrome has safe fallbacks before customer config exists.

The governance spec owns the deferred model.
No support-dev page should imply operators can configure whitelabel settings today.