A server component reads the request host, resolves branding, and hands it to the sign-in client. On the apex or an unknown host the platform default is used instead. The same lookup feeds the page's favicon and social card, so the tab icon and the header agree.
Also called: login page with our logo · branded login · company login screen
- 1SignInPage reads the Host header on the server and calls resolveTenantBranding().
- 2The resolved logo, company name and brand colour are passed into SignInClient as props.
- 3The branded sign-in card renders that header above the method picker.
- 4The accent colour used by the primary button is driven by the tenant's brand colour.
The module comment ties the two surfaces together deliberately: 'White-label-aware sign-in page. Tenant detection lives in lib/tenantBranding so the same lookup feeds the root layout's favicon + OG metadata.' Splitting them would have produced the common half-branded result — the right logo in the header and the platform's icon in the tab.
- Staff on a builder's own address were greeted by unfamiliar platform branding.
- Branding drifting between the tab icon and the page header.
See it on your own jobs
Twenty minutes, your numbers, no slide deck. We’ll build one of your real buildings in front of you and send you the estimate link at the end — yours to keep either way.
or keep browsing features →