Admins pick light, dark, or system mode for the whole organization. The brand color drives buttons, active sidebar items, focus rings, and hover states — in both modes — without a single CSS override.
Your dashboard isn't a generic admin console — it's part of your product. Dashboard theming lets you pick light, dark, or system mode for the entire organization and have your brand color flow through every accent the UI uses. One Save button, two minutes of setup, no developers.
From Settings → Branding, admins and owners control three things that compose into a single coherent look:
The whole dashboard adopts the choice instantly for every member of the organization. Non-admin teammates see the chosen theme; only admins/owners can change it.
Themes stack cleanly because each layer touches a different set of CSS variables:
--primary, --ring, --accent, plus the sidebar variants. Buttons, active nav items, focus rings, and hover states all adopt the brand color in both modes.Because the brand color only paints accents, you never get unreadable text on a mid-tone background or a light button that disappears in dark mode. The system also picks the right text color automatically — black text on light brand colors, white text on dark — using the WCAG luminance formula. You can override that pick if the design calls for it.
Most theming systems break for light brand colors. A pale yellow brand on a Save button shouldn't produce a barely-visible accent on hover. The accent tint algorithm checks the brand's lightness: dark and mid brands get a *lighter* tint, already-light brands get a *darker* one. Either way, there's a meaningful contrast step between primary and accent — so hover and focus states always read clearly.
When an admin changes the theme, a broadcast event triggers every open dashboard tab in the same browser to refetch and reapply — no reload needed. Across devices and other members, the new theme appears on the next page load.
Theming applies to the organization dashboard and the public help center. Marketing pages, docs, and login stay light by design — they're shared across all customers and shouldn't follow any one organization's brand. The framework forces light mode on those routes, so navigating from a dark dashboard to the login page resets cleanly.
A dashboard that matches your brand isn't a cosmetic detail. It's the signal that the platform is *yours*, not a generic SaaS tool you're renting. When your support team and your knowledge base authors log into something that looks like your product, they treat it like part of their work — not a third-party admin panel they tolerate. And when a customer visits your branded help center, the experience reinforces who they're getting support from, not who built the underlying tool.