- Shipped
- August 26, 2026 at 7:29 PM UTC
- Author
- Kamo
- Commit
- 04d302d
The overlay derived its theme folder from the browser's hostname. On the shared meet host that is the platform's for every tenant, so the CSS, favicon and logo loaded on first paint were KamoCRM's whatever meeting you were joining — and for an org with no domain of its own there was never a second chance to be right. The sidecar already resolves which organization a room belongs to (by room prefix, then ?org=, then the host). It now says which FOLDER that organization's branding lives in — its alias — and the overlay re-paints from it once the answer arrives. The first paint still uses the serving host, because there is nothing else to go on before the round trip; the stylesheet is replaced rather than appended so the two do not both end up in the cascade. /api/branding does the same for Meet's own dynamic-branding endpoint, which had the identical derivation.