A brand system with four blocks — Identity (three logo slots and company name), Appearance (light/dark plus accent, header bar, heading, body and page background colours), Customer-facing style (the portal's own palette and typography), and Footer — plus a live preview of a real email rendered on the settings as they are being edited.
Also called: brand settings · company colours · make emails look like my brand · white label
- 1Values save to the tenant's invoice settings: legacy columns stay in sync while the richer set, the extra logos and the appearance land in a brand_tokens JSON column.
- 2Resolution lives in the shared email brand library, so the preview is rendered by exactly the code that sends.
- 3The portal keeps its own token sub-namespace, deliberately separate from the email tokens.
- 4The panel paints from a cached copy instantly, then replaces it with the live row.
The comment states the design goal: set it once and every email restyles, with resolution in one library 'so the live preview is exactly what sends'. The portal sub-namespace has its own reasoning: 'an inbox and a signed document want different surfaces, and one should never silently restyle the other.' Cache-first painting is noted as the panel used to show nothing and then fill in.
- Customer-facing email carried no tenant branding.
- There was no way to see how a brand change would actually render before saving.
- Email styling and portal styling were entangled.
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 →