The Assumption
Give client administrators complete freedom to apply their corporate brand colours to any interface component.
Enterprise Systems Multi-Tenant Architecture & Accessibility
The platform is an enterprise data governance tool deployed across multi-tenant environments, including healthcare organisations and public sector agencies.
Changing a tenant’s branding took custom CSS or an engineering ticket. To support institutional white-labelling, executive management proposed an open colour picker allowing administrators to freely rebrand the user interface. However, unrestricted customisation posed a severe usability risk: non-designer admins could unintentionally choose low-contrast colour combinations, making dense data views unreadable and violating mandatory accessibility requirements (WCAG 2.1 AA).
Give client administrators complete freedom to apply their corporate brand colours to any interface component.
To prevent unrestricted branding from breaking usability, I designed a governed theming workflow. We gave client administrators control over key brand touchpoints, while embedding clear WCAG 2.1 AA guardrails, luminance rules, and validation checks to protect readability across enterprise workflows.
A focused theme editor letting administrators rebrand key touchpoints while preserving data readability.
A simple system rule for developers: administrators pick one base colour, and every interactive state is calculated from it.
Extending the same logic to navigation drawers and dense data tables.
A visual comparison matrix I presented during a team meeting to demonstrate why colour guardrails were critical for real users.
A designed preview in the theme’s details panel to help administrators see the impact of their colour choices before publishing.
Changing visual themes in an enterprise multi-tenant tool directly affects active users across organisations. To prevent critical mistakes and broken layouts, I designed 3 clear safety mechanisms into the publishing workflow.
Preventing critical system errors by locking the baseline theme.
Explaining the immediate impact of publishing a theme to active users.
Keeping custom CSS as a secondary fallback for technical teams, not the primary tool.
To launch quickly while keeping enterprise standards high, our team prioritised core functionality for the MVP and moved advanced educational tools to the next release.
Launched the administrative customiser, allowing enterprise clients to rebrand key portal areas on their own without filing custom engineering tickets.
Integrated baseline WCAG 2.1 AA contrast checks, automatic label colours (white or near-black) and state colours calculated from one base colour, so components stay accessible by default.
The default system theme stays locked, and a confirmation step warns admins before a new theme reaches active users.
While the contrast rules launched in the MVP, the interactive preview simulating colour blindness was documented as a Phase 2 feature for future sprints.
Since this project was designed in Adobe XD before native design token plugins were widespread, maintaining consistency required clear and simple handoff documentation.
Documented every state as a rule on the base colour: +30% black for hover, +30% white for pressed and 40% opacity for disabled; the selected sidebar item or table row uses the full colour, with a 35% tint on hover and +8% black when pressed; labels switch to white or near-black, whichever contrasts more.
Worked closely with frontend developers so they could turn these rules into one shared stylesheet function, keeping component behaviour consistent across any client palette.
--selected: var(--brand);
--hover: color-mix(in srgb, var(--brand) 35%, var(--surface));
--pressed: color-mix(in srgb, var(--brand), #000 8%);
--on-brand: contrast-pick(var(--brand), #FFF, #12141A);
In enterprise tools, unlimited user freedom often leads to broken interfaces. Designing sensible boundaries - like locking core text contrast and restricting brand customisation to key areas - protects legibility without frustrating administrators.
When an administrative change affects hundreds of daily users, UX safety is essential. Adding confirmation warnings and locking the default system theme guards against critical mistakes while keeping the configuration workflow straightforward.