The Branding surface decides what your users see at the moments that matter: the sign-in page, the password-reset email, the welcome email after signup. Default brand is a neutral platform default; you replace it with yours.
What's customisable
Section titled “What's customisable”- Logo + favicon — your wordmark on the sign-in page; your favicon in the browser tab. See Logo + favicon.
- Theme colours — primary brand colour, applied to buttons / links / focus rings. Optional accent colour. See Theme colours.
- Custom CSS — for fine-grained control beyond the colour knobs. See Custom CSS.
- Email templates — verification, recovery, OTP. See Email templates.
What's NOT here:
- Sign-in copy (the form's labels, button text, error messages) — those live in Branding → Sign-in page → Copy, not on a separate page. Mentioned for completeness.
- Email sender (the From name + reply-to). Lives in the SMTP integration — see Email SMTP.
- Custom domain for the sign-in page (
auth.cymmetri.cominstead of<tenant>-<org>.intelliauth.local). Set up in Settings → Custom domain — a separate, more involved process (DNS + TLS).
When to brand
Section titled “When to brand”Brand before going live to real users. A neutral platform sign-in page works for prototypes but conveys "this isn't really us" to your customers.
Two paths:
- Light brand (5-10 minutes) — logo + primary colour + a custom From-name on emails. 80% of the impact.
- Full brand (a few hours) — logo + colours + favicon + custom CSS + every email template re-written + custom domain. 100% of the impact; meaningfully more polished.
Most production tenants do the light brand at launch and the full brand within a quarter.
How it propagates
Section titled “How it propagates”Branding changes apply immediately to the next sign-in / email. There's no rollout; no caching; no waiting. Save → live.
The exception: if a user has the sign-in page open in their browser when you change the logo, they'd need to refresh to see the new one. Real users don't notice; you might in testing.
Preview before saving
Section titled “Preview before saving”The Branding surface has a live preview. As you change a colour or upload a logo, the right pane shows the sign-in page with your changes applied. Save once you're happy.
For email templates, the preview shows the rendered email with your template + your branding applied. Send-a-test-to-myself button lets you confirm rendering in your actual inbox (Gmail / Outlook / etc. render differently than the preview iframe; the test-send catches surprises).
What stays default
Section titled “What stays default”Anything you don't customise uses the platform's default. The platform default is intentionally bland — grey / neutral / generic copy. It works; it just doesn't look like you.
Per-application branding
Section titled “Per-application branding”The branding here is tenant-wide — all of your tenant's applications share the same sign-in page styling. If you need per-application brand (different logo for "Cymmetri Banking" vs "Cymmetri Investments"), the platform supports a per-application branding override on the application's settings page. The basic branding pattern still applies; you override specific fields per application.
For most tenants, the tenant-wide brand is enough.
Every branding change records an audit-log entry with before/after. Useful for "why did the sign-in page change last Tuesday?" investigations.