- Shipped
- August 25, 2026 at 10:17 PM UTC
- Author
- kamo
- Commit
- 833081c
Colours, logos and backgrounds chosen while creating an organization were not reaching it. The member opened their new workspace on default branding and had to set all of it again from Settings, which is where the bug was reported from. None of it is what the workspace reads. The theme is a generated globals.css and config.json in MinIO, and until provisioning runs there is nothing there to serve — the colours sit on the org row and the uploads sit in the bucket, unreferenced. Nothing called it. Provisioning was triggered by /setup/dns when a domain verified, which was the only way into a new org back when one could not be entered without a domain. The wizard goes straight into the org now, and a domain is optional, so that trigger reaches neither the orgs that skip a domain nor the ones that never open the page. It belongs to creation, the same way the trial did. Runs last, after the uploads, so the theme is built from them. Non-fatal like the uploads themselves — the org exists and Settings can still fix it — but reported as a warning rather than swallowed, because opening on the wrong branding with no explanation is the failure being removed. A domain-less org still resolves: SecurityService falls back to {alias}.kamocrm.com, the same name the client derives.