- Shipped
- September 11, 2026 at 3:00 AM UTC
- Author
- Kamo
- Commit
- 7d80fa7
Two more columns in the vocabulary home_logo_overlay established: a token, not a hex, so an org that rebrands keeps an overlay that matches its new colours. Both nullable with no backfill - null is NONE, which is what every org looks like today. nav_logo_overlay paints the simple logo at the top of kamo-internal's primary nav rail. Its own column because the rail is a darkened shade of the primary colour; the home page's white masthead rarely wants the same shade. Delivered through OrgContext like its home page sibling. careers_logo_overlay paints the header logo on kamo-careers. That site has no OrgContext, so securityservice bakes the resolved colour into the theme config.json, the route login, register and apps already take. patchOrganization is an ALLOW-LIST, so both names go there too, and a new test walks every overlay the settings page sends - not just these two - because a column the method does not name is accepted with a 200 and never stored. Proven by removing the two new lines: 3 of its 4 cases fail. The columns were added to the live orgs table by hand before this push (ddl-auto is none and InitializerService is not deployed): ALTER TABLE orgs ADD COLUMN IF NOT EXISTS nav_logo_overlay VARCHAR(24); ALTER TABLE orgs ADD COLUMN IF NOT EXISTS careers_logo_overlay VARCHAR(24);