Branding and White-Labeling

Why this area exists#

The Branding section lets your organization carry its own identity across shared public layouts and tenant-branded email layouts instead of relying only on platform defaults.

Confirmed branding fields:

• Logo
• Primary Color
• Secondary Color
• Contact Email
• Contact Phone
• Website
• Header Content
• Footer Content

What changes after configuration#

Logo and colors#

The tenant logo and colors are used in:

• shared public page layouts
• tenant-branded email layouts
• BBMS inline checkout branding when that payment path is used

When no logo is uploaded, the platform falls back to branded initials or text styling rather than a blank header.

Header and footer content#

Public pages use special logic here:

• if Header Content is blank, the standard public header shows the brand mark and optional website link
• if Header Content has meaningful content, that content replaces the simpler header treatment
• if Footer Content is blank, the footer falls back to the organization name and contact email
• if Footer Content has content, that custom footer is shown instead

This makes header and footer content powerful but also easy to misuse. Rich text here can affect every shared public page.

Contact details#

Workspace contact fields are used in multiple tenant-branded places, including:

• public header and footer layouts
• event public pages and waitlist offer pages that fall back to tenant contact details
• tenant-branded email footer content

These fields are organization-wide defaults, not substitutes for event-specific contacts when a single event needs a different owner.

What public pages inherit tenant branding#

Confirmed tenant branding appears in shared public layouts used by:

• public donation pages
• public event pages and registration flows
• public program pages and checkout flows

Tenant branding is also used in tenant-branded email layouts.

Auth and member-facing experiences can also use tenant branding when the request is running on the resolved tenant domain.

What remains platform-level#

Workspace branding does not control everything.

• There is no tenant favicon setting in this area.
• Public media files are still served from the central app storage origin.
• Stripe webhooks remain on Altrinum's hooks domain.
• Some mail-domain behavior still depends on platform mail configuration, so the sender preview matters more than assumptions.

Setup guidance#

1. Open Workspace Settings > Branding.
2. Upload the logo.
3. Add your primary and secondary colors.
4. Fill in contact email, phone, and website.
5. Add header or footer content only if you want content that should appear across shared public pages.
6. Save the settings.

Operational notes#

• Keep header and footer content short and broadly applicable. This area is best for persistent organization messaging, not campaign-specific copy.
• If you use a branded website link in the header, confirm it points to the correct public site or home page.
• If your team changes colors near a major launch, test both public pages and emails. Email color rendering can surface issues that a browser preview does not.

Common mistakes#

• using tenant-wide header content for campaign-specific messaging
• assuming contact fields update event-specific contact blocks that are configured separately
• forgetting to test email branding after changing logo or colors
• expecting a favicon or deeper site theme controls that do not exist in this section

What to test after changes#

• one public donation page
• one public event page
• one public program page
• one tenant-branded email
• one BBMS checkout preview if your organization uses BBMS

Related topics#

• Workspace Basics
• Custom Domain Setup
• Organization Address and Contact