Keep workspace, chat and KB colors independent
Coordinate your support surfaces while keeping the right color controls for each area.
On this page
Overview
Three checkboxes, one per surface (Launcher, Chatbox, KB), default checked. Admin Theme is a fourth, independent store (es_theme).
When to use this
A purple admin shell should not force a purple help center if the KB uses custom blue.
Where to find the controls
Each Experience Builder page has the inherit checkbox above the color fields.
Who can make these changes
Support Admin.
Before you begin
Checked = inherit Theme Builder tokens. Unchecked = independent sanitized colors. Restore by checking the box again; saved custom hex is kept but unused until unchecked.
Follow these steps
Set Admin Theme, then test launcher inherit vs chatbox/KB custom. Change Admin Theme again and confirm only inheriting surfaces follow.
Settings reference
Colors are hex or simple rgb/rgba. Scripts and CSS injection are stripped.
Example workflow
See the color independence test in EXPERIENCE_VERIFICATION.md.
Good practices
Do not copy all tokens into es_experience. Only preset_id + sparse overrides.
Important considerations
Public endpoints never accept color writes.
If something does not work
If a custom surface suddenly follows admin, the inherit checkbox was left checked.