Skip to main content
Organisations can have multiple communities with different brands — a sportswear store with regional communities, a media company with audience-segment communities, etc. Each community can override the org theme with its own colours, fonts, logos, and UI settings.

​
Where to find it

Community Settings -> Branding & Theme.

​
What you can override

Colours

Primary, accent, destructive, success, warning, sidebar — all overridable per community.

Logo + banner

Per-community logo and community banner.

Fonts

Override the org’s font with a community-specific choice.

Tab visibility

Which member-facing tabs show (#2353). Hide Games for communities without games, Shop for progression-only communities.

Per-step challenge-complete colour

The celebration screen colour (#2204) can differ per community.

Widget loading state

Customise the widget loader per community.

​
Live preview iframe

The live preview iframe (#2305) on the right shows your changes in real-time — no save-and-refresh cycle. The theme editor has accessibility improvements, undo, and iframe sync (#2358) so changes never feel laggy.

​
Community description & theme flag

Each community has a description and an “active theme” flag (#1404) — controls whether overrides apply (on) or the org theme cascades through (off).

​
Community theming v2

#1545 introduced v2 community theming — a more comprehensive override set. If you’re migrating from v1 (legacy), the admin handles the transition; existing overrides continue to work.

​
The unified theme system

All of this runs on the unified theme system (#1874) — a single data model that covers:
  • Admin shell chrome (sidebar, top nav, buttons)
  • Member app (bottom nav, feed, wallet, profile)
  • Widget embeds
  • Email templates
Change a colour once, it propagates everywhere. See Branding & Appearance for the org-level counterpart.

​
Strategy

Keep community themes similar enough to feel like one family. Cross-community navigation should feel like a coherent brand, not jarring gear-shifts.
Use tab visibility overrides sparingly. If you hide the Shop for three communities, maybe rethink whether those communities need Shop support at all (vs. a permanent org-level feature toggle).
Overriding too many tokens leads to visual drift and inconsistency. The cleanest pattern: override primary colour and logo for brand identity, inherit everything else.