Branding makes a tenancy look like the client’s own. Each client carries its own logos, colours and login screens on the shared platform, so the experience reads as theirs rather than a generic install.

This guide covers:

• Setting a tenancy’s logos, colours and login screens through its configuration
• Carrying the client’s branding into the header of the emails GSA sends
• Configuring the from, reply-to and BCC addresses used for that client
• Applying branding through the framework layer’s per-client hooks, not a separate build
• Pairing branding with the lighter customisations — permission rules, dashboards and FAQ — that travel with it

Set this once and every screen and message a client’s people see carries their identity.

💡 Power User Insight: Branding sits at the tenancy level with a System Administrator, separate from a Site Admin’s workflow setup. It’s one of the lighter customisations that reuses cleanly across clients.