Email is one of the few things a client interacts with daily, and on most hosted platforms it announces somebody else's company every time they log in. Domain branding replaces that: your logo, your colors, your support contacts, on your own web address, with nothing on screen naming us.
This page covers what can be changed, what happens with the certificate and DNS, and the difference between branding a single domain and branding the whole account.
What Domain Branding Actually Changes
A brand profile holds the visual identity and the contact details that replace ours:
| Setting | What it does |
|---|---|
| Logo, light and dark | Two versions, so the interface looks right in either theme |
| Favicon | The browser tab icon, which is the detail people forget |
| Primary and accent color | Applied through the interface rather than pasted on top |
| Custom domain | Webmail served from your address instead of ours |
| Support URL and email | Where users go when stuck — your desk, not ours |
| Transactional sender | The address system messages come from |
That last pair matters more than the colors. A user who can't log in will contact whoever the interface tells them to contact. Domain branding without changing the support details means your clients raise tickets with us about a product they think is yours, which is the worst of both arrangements.
Per Domain or Per Account
A brand profile has a scope, and choosing it correctly is most of the setup.
Account scope applies everywhere by default. This is what you want when the whole account is one company — one identity, applied once, no per-domain administration.
Domain scope attaches a profile to a single domain. This is the agency case: each client domain carries that client's identity, and their staff see their own company when they log in, not yours and not ours.
The two combine sensibly. An account-level profile covers everything you haven't specifically overridden, and a domain-level profile wins where it exists. So you can brand your own domains as your company, and give three particular clients their own domain branding, without configuring every domain individually.
The Custom Domain and Its Certificate
Serving webmail from your own address is the part with moving pieces, because it involves DNS and TLS rather than just an upload.
You point a hostname — typically mail.yourdomain.com — at us with a DNS record. Once it resolves, a Let's Encrypt certificate is issued for it automatically, and the platform tracks its expiry and renewal rather than leaving you to remember. Alongside that, several checks run continuously: the A record, PTR, SPF and HELO, each reported individually so a failure names itself instead of presenting as "it doesn't work".
Those checks exist because domain branding touches sending as well as appearance. If system messages come from your address, that address needs to be authorized to send, or they'll land in spam and users will conclude the platform is broken. The SPF check catches exactly that, and setting up SPF covers the record itself.
Certificate issuance isn't instant. Expect the DNS to propagate and the certificate to be issued before the address works, which is usually minutes and occasionally longer.
The Boundary That Stays Ours
Being honest about the boundary avoids an awkward conversation later.
Domain branding covers the interface your users see. It does not rewrite the mail servers' hostnames, so anyone inspecting message headers can see where the mail was handled — that's true of every white-label email arrangement, including ones that don't say so. Your clients won't see it; a technically curious recipient could.
Nor does it change protocol endpoints for IMAP and SMTP unless you configure them separately. Users setting up Outlook or a phone will see server addresses, so if a fully branded experience matters, that's the piece to plan for rather than discover.
Getting It Right the First Time
A few practical points, learned from setups that needed redoing.
- Supply both logo versions. One logo across both themes means dark text invisible on a dark background, and it looks careless in exactly the place you were trying to look professional.
- Check the favicon. It's the single most-overlooked element and the one visible on every open tab all day.
- Test the colors against real content. A brand accent that works on a website can be unreadable behind body text.
- Set support contacts before announcing it. The moment users see branded webmail, they'll treat it as your product and contact whoever it names.
- Verify the DNS checks pass rather than assuming. They're there to be read.
Where This Sits Against Full White Label
Domain branding covers the webmail your users log into. It's included on every plan, and for most businesses that's the entire requirement — staff and clients see the company they expect.
The separate White Label Lite subscription, at $39 a month or $389 a year, extends the same idea to the dashboard where domains and mailboxes are administered, which is what you need if clients manage their own accounts rather than only using mail. It also carries 10% off current Drive prices while active.
The distinction is simply who logs in where. If your clients only ever open webmail, domain branding is enough. If they also administer their own domains, the dashboard needs branding too, and that's the paid add-on.
Pairing branding with a per-domain signature keeps the whole presentation consistent, since the signature is the part recipients outside the company actually see — that's covered in per-domain signatures.
The Elements Users Actually Notice
Having watched a number of these rollouts, the elements that register with ordinary users are not the ones people spend their time on.
The login page is the whole first impression, because it's the one screen a user sees before they have any context. If it carries the right logo and the right colors, everything after it is assumed to belong to the same company, even where the styling is neutral. Get that screen right and the rest matters much less than you'd think.
The browser tab is second, and it's the one people skip. Users keep webmail open all day alongside a dozen other tabs, and the favicon is how they find it. A default icon there quietly undermines everything else, because it's the piece of the interface visible most often.
System emails are third and the most commonly neglected. Password resets, storage warnings and login alerts arrive in the user's inbox with a sender address and a support contact. If those still name us, the domain branding stops at the edge of the interface and the illusion breaks precisely when the user is already frustrated.
What almost nobody notices is exact color matching. Getting within a shade of your brand palette is fine; the difference between correct and nearly-correct is invisible to everyone except the person who chose the color.
Rolling It Out to People Already Using It
Applying domain branding to a live user base needs slightly more care than setting it up on a new one, because the interface changing overnight looks like a security incident to a cautious user.
Tell people first, briefly, and say what will change. One short message describing the new appearance and the new web address prevents a run of "is this a phishing site?" tickets, which is the predictable outcome of silent rebranding.
Keep the old address working during the transition rather than cutting it off. Bookmarks and saved passwords point at the previous URL, and a redirect gives people time to update without a support conversation each.
Change the support contacts at the same moment as the visual identity, not afterwards. A branded interface pointing at our support desk generates tickets we can't usefully answer, because we don't know who your users are or what you've told them.
If you're branding several client domains, do one first and leave it a week. The problems that surface — a logo that doesn't work on dark, a color that fails against body text, a DNS check that didn't pass — are much cheaper to fix once than thirty times.
When Branding Is Worth Skipping
It isn't automatically correct for every account, and there are two cases where leaving it alone is the better call.
If your users are internal staff who know exactly which platform they're on, domain branding is decoration. It does no harm and it solves no problem, and the setup time is better spent elsewhere.
And if you're a reseller who intends to be visible as an intermediary rather than invisible, partial branding can read as evasive. Some clients prefer knowing which platform sits underneath, particularly where they're responsible for their own compliance. That's a positioning decision rather than a technical one, and it's worth making deliberately instead of by default.
