One organization. One brand. Every product.
v1.18.0 makes organization branding a shared platform setting, extending the same identity across products and email.
Configure once, carry it everywhere
The foundations release dated 2 October 2026 establishes one organization-branding setting in User Directory → Branding. Once configured, it applies across legacy products, every KC Native suite, internal and administration tools, and email. The previous per-product entitlement rule is superseded; de-branding remains a separate product-level question.
More than a primary button colour
The tenant colour replaces the complete suite colour chain: primary states, fills and tints, text on primary surfaces, accent text, links, and focus borders. A branded surface should not retain a competing suite accent in its product sub-name or email source-product label. The product-category attribute remains in place as the fallback and an audit hook.
A consistent identity in every slot
The tenant logo belongs in headers, drawers, sign-in, the product switcher, and email header cards. The tenant favicon follows into every product. The organization name replaces the KnowledgeCity brand-block line and becomes the email sender name. A configured tenant font replaces Lato as the Latin face, retaining weights 400 and 700.
What this release does—and does not—ship
This is a minor rules and documentation release: no token is renamed, no selector changes, and tokens.json is unchanged. The article describes the updated foundations contract; it is not a claim that every product has already adopted it.
Dark mode for tenant colours remains open because the Branding preview is light-only. The mobile system adopts the decision in its own release. Custom domains, login backgrounds, colour-mode defaults, and email-from settings are not part of the current Branding inventory.
What to check next
Review the full branded experience, including less visible logo slots, focus states, links, and transactional emails. ADR 037 also records that the existing Branding-page statement about newer apps keeping their built-in colour contradicts the new decision and needs a product-copy update.
Read the complete v1.18.0 release notes →
Read ADR 037 →