Dedicated Notification Email Domains Added for Multi-Brand SaaS
TL;DR
Multi-Brand SaaS agencies can now configure dedicated notification email domains for up to two brands.
TL;DR
Agencies running Multi-Brand Management can now assign dedicated notification email domains to up to two brands. If you run multiple brands, configure your DNS records to stop sending platform notifications from a shared sender.
Who this affects
This applies to agency operators using Multi-Brand Management. HighLevel has not confirmed which specific subscription tiers have access to this feature, nor has it confirmed the broader rollout status. Agencies running only a single brand do not need to take action.
What changed
- Agencies using Multi-Brand Management can configure a dedicated notification email domain or subdomain for up to two brands.
- System notification emails now send from each individual brand's domain instead of a shared sender domain.
- A dedicated Notification section now displays each brand's domain, setup requirements, and verification status.
- You can add, verify, update, or remove notification domains independently using DNS records.
- If a brand does not have a configured notification domain, system emails will fall back to the default brand's notification domain.
- HighLevel has not confirmed whether this replaces or breaks prior sender configurations, nor have they published specific plan gating beyond the two-brand limit.
Where to find it
Go to Agency Settings > Email Services > Dedicated Domain and IP > Notification.
How agencies will use this
An operator managing two separate white-label SaaS offers can now isolate system-level emails between both properties.
You set up the required DNS records for your secondary brand under the new Notification settings. When a sub-account tied to that secondary brand triggers a system notification email, the recipient sees the notification originating from that specific brand's domain. If you do not add DNS records for the second brand, the platform automatically routes its notifications through your primary default brand's domain instead.
Our take
This is a major fix for multi-brand operators who care about clean white-label delivery. Having system notification emails leak a default brand or a shared domain creates confusion for clients on secondary brands. The cap is currently set at two brands, but setting up the DNS records immediately resolves brand mismatch issues across your sub-accounts.
Source: Official HighLevel announcement


