Currently, when customising panels, callouts, and info boxes in the new Confluence Cloud editor, users can only choose from a rigid 7×3 palette of 21 predefined preset colours (see attached screenshot).
We would love to see Atlassian introduce the ability to use custom brand colours—either via custom HEX/RGB input or, even better, site-admin-defined corporate colour palettes.
Current limitations
- Strictly fixed palette: Users cannot enter a HEX code (e.g.,
#0052CC or #FF5630) or adjust shade intensity. - Generic presentation: Internal portals, bid proposals, and team documentation often look generic or clash with established company design guidelines.
- No central governance: Space owners and admins cannot establish a consistent visual language or corporate palette across spaces.
Proposed solution
- Custom colour input (HEX/Colour picker):
- Add a
+ / custom colour picker button or HEX input field directly beneath the preset swatch grid.
- Organisation brand palette (Admin configurable):
- Allow Site Admins (or Space Admins) to define a custom palette of 4–8 brand colours that automatically populate alongside or above the default presets for all contributors.
- Built-in WCAG contrast check (Bonus/best practice):
- If custom background colours are selected, provide an automatic high-contrast text toggle (dark vs. light text) or an accessibility indicator to ensure readability.
Why this would be valuable
- Brand alignment & professional finish
Confluence is frequently used not only for internal technical notes but also for client-facing knowledge bases, tenders, proposals, brand guidelines, and onboarding hubs. Being limited to generic default pastels makes documentation feel like an integrated, professional extension of our brand. - Consistent visual taxonomy & information architecture
Teams rely on callouts to signal specific types of information (e.g., Actions, Decisions, Architectural Warnings, Compliance Notes). Having organisation-level brand swatches lets organisations standardise semantic colour coding across departments and project spaces. - Eliminates clunky workarounds
Currently, users work around this limitation by using single-cell tables, custom banner graphics, or third-party marketplace apps to match brand aesthetics, adding unnecessary friction to page authoring. - Consistency with modern design systems
Modern collaboration and design tools (Figma, Miro, Notion, Canva) treat brand palettes as standard functionality. Bringing this into the Atlassian Editor elevates Confluence’s polish for design-, architecture-, and branding-conscious teams.
