Skip to content
IntelliAuth

Logo and favicon

The most visible branding element. Upload once; users see it on every sign-in.

Section titled “Logo”

Branding → Logo. Upload an image.

Specs:

  • Format — SVG preferred (scales crisp at any size). PNG @2x acceptable (~600×120 px) for raster wordmarks.
  • Aspect ratio — wider than tall. Wordmarks (text + icon) look best at ~5:1. Square icon-only is okay but reads as "we forgot the wordmark".
  • Colours — should look good on both light and dark backgrounds. The sign-in page can be either; users may have dark-mode preferences. SVGs that use currentColor for fills adapt automatically.
  • File size — under 100KB. SVG is usually much smaller; PNGs over 100KB make the sign-in page sluggish to load.
  • Transparency — recommended. The sign-in page's background colour comes from theme colours; your logo sits on top.

Save. The logo shows on the sign-in page immediately. Preview pane on the right confirms.

Favicon

Section titled “Favicon”

Branding → Favicon. Upload a square image.

Specs:

  • Format — SVG preferred. PNG 64×64 (or larger square) acceptable.
  • Aspect — square, 1:1.
  • What it should look like — the icon part of your wordmark. Recognisable at 16×16 pixels (the favicon's display size in most browser tabs).

Browsers render the favicon in the browser tab, in bookmarks, in browser history. Make it distinct enough to recognise.

Dark mode

Section titled “Dark mode”

If your tenant's sign-in page supports dark mode (most platform tenants do; user-prefs-driven), upload a dark-mode-specific logo + favicon as well. Optional but recommended for polish.

Branding → Logo (dark mode) and Branding → Favicon (dark mode). Same specs; just designed for dark backgrounds.

When you don't supply dark-mode variants, the platform's auto-inversion logic kicks in — usually fine for SVGs that use currentColor; sometimes awkward for fixed-colour PNGs.

What if I have multiple brands?

Section titled “What if I have multiple brands?”

Per-application branding overrides exist (mentioned in Branding overview). If "Cymmetri Banking" needs a different logo from "Cymmetri Investments", override the logo on each application's settings page; the tenant-wide default is the fallback.

Common gotchas

Section titled “Common gotchas”
  • Logo too big. A wordmark designed for a website header may be too large for the sign-in page. The platform scales down automatically, but very wide logos crop. Keep aspect to ~5:1 or narrower.
  • Logo with white background. Looks fine on the white sign-in page; looks terrible on the dark-mode page. Make the background transparent.
  • PNG without @2x. Looks pixelated on high-DPI screens. Either use SVG or upload at 2x resolution.
  • Favicon too detailed. A complex icon doesn't read at 16×16. Simplify; or just use a single letter / shape that's recognisable.

Audit

Section titled “Audit”

Uploading a logo / favicon records branding.logo_updated / branding.favicon_updated in audit. Includes a checksum of the new file; useful for "is the file on the platform the same one I uploaded?" verification.