On this page
What a branded client portal covers
"White label" means different things to different vendors. It helps to break branding into layers and check each one:
| Layer | What the client sees | What it takes |
|---|---|---|
| Visual identity | Your logo, colours and browser tab icon | Uploading assets and picking a brand colour |
| Web address | portal.yourcompany.com instead of the vendor's domain | A DNS record and a security certificate |
| Sign-in | A sign-in page with your logo and welcome text | Settings on the custom domain |
Notifications from support@yourcompany.com | Verifying your domain with DNS records | |
| Documents | Your logo on reports, exports and certificates | A separate logo upload or report template |
| Other surfaces | Your name on a desktop, Teams or mobile app | Varies widely by vendor |
Why branding matters to clients
Branding is not vanity. It changes how clients react to the portal:
- Trust. A sign-in page and emails that clearly come from their IT provider are less likely to be mistaken for phishing, and clients are more willing to enter their credentials.
- Familiarity. Clients recognise the portal as part of the service they pay for, not an extra tool someone signed them up for.
- One relationship. Reports, invoices and support all appear under the same name the client sees on contracts and in meetings.
Custom domains and email: the DNS part
Two branding features need someone with access to your DNS:
- A custom domain usually needs a CNAME record for a subdomain such as
portal.yourcompany.com, sometimes with a verification record. The vendor then issues a security certificate so the address works over HTTPS. - A custom sending domain for email needs records that authorise the vendor's mail service to send on your behalf, such as SPF and a DKIM key. DKIM is defined in RFC 6376, and verifying your domain this way improves trust in your messages, although it never guarantees inbox placement.
Use the exact records the vendor gives you, rather than generic examples copied from another guide.
Questions to ask a vendor
- Can I use my own domain, and is a certificate set up for me?
- Can the sign-in page show my branding, and which sign-in methods can I offer on it?
- Do notification emails come from my domain, and can I edit their wording and add my logo?
- Do generated reports and exports carry my logo?
- Does the vendor's name appear anywhere clients will see it, such as page footers, system emails or embedded widgets?
- If I have several brands, can I use more than one domain?
How MSPortal handles branding
MSPortal lets MSP administrators brand the portal from Settings > Tenant > Branding or the branding step in Launch Center. According to the MSPortal branding guide, you can set:
- Brand colour: one primary colour from which MSPortal builds light and dark variants, applied to buttons, links, badges and the sidebar for every user.
- Logos: a primary logo and a small icon for light mode and for dark mode, plus a favicon for browser tabs on your custom domain.
- Reports logo: a separate logo for generated reports, documents and training certificates.
- Custom domains: add a domain such as
portal.yourcompany.com, add the routing and verification records MSPortal shows, and SSL is set up automatically once DNS is ready. You can add more than one domain and choose the primary one. - Sign-in page: on your custom domains, set the background, logo size, welcome title and subtitle, and help instructions, and choose which sign-in methods to offer: Microsoft, Google and an emailed magic link.
- Email sender: verify a sending domain with the DNS records shown, then send portal notifications from an address such as
support@yourcompany.com. Email templates can be edited, and you can insert your company logo into them. - Portal name and support details: the name clients see, plus the support email, phone and website shown to clients and used by the AI assistant.
The same branding carries into the storefront, dashboards and other modules, so you set it up once. MSPortal can also generate a branded Microsoft Teams app with your name, logo and accent colour, which is enabled per account on request.
One honest caveat: a few system screens and messages, including the client onboarding workspace footer, some onboarding emails and the embeddable satisfaction-survey widget, show a small "Powered by MSPortal" line. Check those placements during your setup if full white labelling matters to you.
See the branding in context in a demo, or check what is included on the pricing page.
Related questions
What does white label mean for an MSP client portal?
It means the portal presents the MSP's brand rather than the software vendor's: the MSP's logo, colours, web address and email sender. The extent varies by vendor, so check sign-in pages, emails, reports and apps individually.
Do I need a custom domain for a branded client portal?
Not strictly, since logos and colours work on the vendor's address. A custom domain makes the portal look like part of your service and, in MSPortal, is required for the branded sign-in page and its sign-in method choices.
Can portal emails come from my own domain?
Usually, once you verify the domain by adding the DNS records the vendor provides. In MSPortal, you add the domain under Settings > Email, verify it, then set a default from address such as support@yourcompany.com.
How do MSPs get clients to use a branded portal?
Branding helps, but adoption comes from easy sign-in and a clear reason to log in. See How do MSPs get clients to actually use a client portal?