Skip to content
Open the app

Brand configuration

Developers2 min read

Each institution gets its own look. Branding is a per-tenant configuration set during onboarding (not a self-serve panel), and it drives both the student app and the staff console so they read as the university's own.

What a brand carries

The brand configuration covers:

  • Identity — the institution name and a short mark.
  • Logos — a primary (light-mode) logo, with an optional dark-mode variant; when the dark variant is omitted, the primary is reused.
  • Colours — the accent colours, with light and dark values plus an accent text colour, so the UI re-themes cleanly in both modes.
  • Type — the body font.
  • Favicons — light and dark favicons; browsers that support media-aware favicons pick automatically, others fall back to the primary.
  • Sign-in — how people authenticate (see below).
  • Crisis overrides — institution-specific crisis copy, resources, and additional trigger phrases (additive to the safe default — see the note).
  • Events link — an optional "browse all events" URL for when the in-app list is empty.

Sign-in configuration

The auth portion declares how the tenant signs in:

  • Mode — domain-based email links, or SSO.
  • For SSO, the connection details live in the SSO configuration (issuer, client id, discovery URL, scopes) — see the OIDC flow. An email fallback can be allowed alongside SSO.
Crisis overrides only ever add to the floor

A tenant can customise crisis copy and resources and add its own trigger phrases, but the built-in safety floor of crisis signals can't be removed. Overrides extend detection; they never weaken it. The institution-facing context is in breach and incident response.

How it's set

Brand configuration is applied during onboarding and managed by First Six — in the console it appears read-only (for example on the term-setup screen) so staff can see the identity without accidentally changing it. To change branding, raise it through onboarding or support.

Branding vs. domains

Branding is what it looks like; a custom subdomain is where it lives. They're independent — a tenant is fully branded on the shared host before any custom domain exists. See custom subdomains.

Common questions

Can we manage our own brand in a dashboard?

Not today — it's set at onboarding and managed for you, which keeps a consistent, accessible result (contrast is checked across themes). Send updated assets through onboarding or support.

Does dark mode need separate assets?

Optionally. A dark logo and favicon are supported; if you don't supply them, the light versions are reused, which is fine for marks that read on both backgrounds.

Where does the crisis copy come from?

The safe default, plus any tenant overrides you provide. Overrides can add resources and phrases but can't remove the default safety floor.

Domains and white-label URLsHow institutions are addressed today (shared app domains with per-tenant branding) and what a dedicated subdomain like unisc.firstsix.com.au involves.The OIDC flowHow First Six does single sign-on — the OIDC authorization-code flow, per-tenant config, and how a login links to a student or staff record.Breach and incident responseWhat First Six does if data is exposed or a breach is suspected — the process, the notification clock, and what your institution can expect.
Was this helpful?
Need more help?

The fastest answer is usually one question away.

Edit this page on GitHub