- Shipped
- November 13, 2026 at 2:13 AM UTC
- Author
- Kamo
- Commit
- 67037a9
/validate runs before the tab has a session. The server cannot resolve ?org= there (the alias lookup is session-guarded), so it fell back to the host -- the platform on internal.<platform> -- and the splash showed KamoCRM's logo, colours and overlay until the redirect. The org's own logo never appeared on it. The org's theme folder is public, so ?org= is now recorded for the tab on the first client render and the splash paints that organization from the start. On the shared host with no ?org= (the MFA path) the logo waits for the session rather than showing the platform's. On success the session's organization and overlay are adopted, the logo crossfades if they differ, and the redirect waits for that logo to load and settle on screen. The overlay comes from the org in context when it is the tab's own, else from config.json's new loadingLogoOverlayColor, else from the session. Square or padded marks get a taller box.