Reselling email works until a client wants to do something themselves. Add a mailbox, reset a password, check why a message bounced — small requests, each one landing in your inbox because there's no way to let them in without letting them into everything. White label client access is the arrangement that solves that: clients administer their own domains, under your brand, seeing nothing they shouldn't.
This page covers what a client can be given, what stays hidden from them, and the questions worth settling before you switch it on.
The Problem With Sharing a Dashboard
Most resellers arrive at one of two unsatisfactory arrangements.
Either the client gets no access at all, and every trivial change becomes a support ticket. That's fine at three clients and unworkable at thirty, and it makes you the bottleneck on tasks with no margin in them.
Or the client gets an account of their own, which means a separate subscription, separate billing, and a relationship where you're a bystander rather than the provider. You've solved the access problem by giving away the customer.
White label client access is the middle path that most platforms don't offer: one subscription, yours, with clients confined to their own domains inside it. You keep the commercial relationship and the billing; they get the self-service that stops them asking you to do their admin.
What Confinement Actually Means
The whole arrangement rests on one property: a client sees their domains and nothing else. Not other clients' domains, not the account-level settings, not the commercial side.
That confinement has to hold everywhere rather than only on the pages a client would normally visit. It isn't enough for a domain list to be filtered — every action that changes something must check the same boundary, or a client who bookmarks a URL or edits an identifier ends up somewhere they shouldn't be. This is the part of white label client access worth interrogating in any platform offering it, because filtering a list is easy and confining every write path is not.
The practical test to apply: ask what happens if a client changes the domain identifier in a URL, and whether the answer is the same for viewing as for editing and deleting. This is broken access control, the most common weakness class in web applications, and multi-tenant dashboards are where it hides best.
The Access a Client Can Hold
White label client access is granted by role and scoped to specific domains, so the question is what a particular person needs rather than what tier they're on.
- Mailbox administration. Creating, renaming and removing mailboxes on their own domains, setting quotas, and sending setup invites so their staff choose their own passwords rather than being handed one.
- Password and access recovery. The single most common support request, handled without you.
- Routing. Aliases, catch-all behavior and forwarding within their domains.
- Diagnostics. Spam statistics and delivery information for their domains, so "why didn't this arrive?" has an answer they can find themselves.
- Read-only access for people who need visibility without the ability to change anything — a client's finance contact, or a junior member of your own team.
Your own staff sit on the same mechanism. Someone handling three accounts can be scoped to those three, which limits the damage from an ordinary mistake as much as it limits deliberate misuse.
The Two Things Clients Never See
Two categories are deliberately invisible under white label client access, and both matter commercially rather than merely technically.
Billing and plans. Clients never see what the platform costs, which plan you're on, or what any other client is paying. This is not decoration — it's the difference between reselling and introducing your clients to your supplier. On a white-label host these surfaces are hidden from everyone, including the account owner, so there's no path by which a shared screen or a curious client reveals your margin.
Everything belonging to other clients. Obvious, and worth stating because it's the assurance you'll be asked for. A client sees their domains, their mailboxes, their statistics.
Consumable resources need thought too. Verification credits on a white-label host draw only on purchased balance rather than a plan's monthly allowance, so a client running a large list check can't quietly exhaust something you were relying on elsewhere.
Knowing Who Changed What
The moment white label client access is switched on and more than one person can change things, you need a record. This turns out to matter most in practice.
An activity record showing before and after values answers the question that actually gets asked, which is never "was something changed?" but "what was it before?" A log saying a mailbox quota was modified is nearly useless; one saying it went from 5 GB to 500 MB at eleven on Tuesday, by a named person, is the whole answer.
This protects you more than it protects the client. When a client insists they didn't delete the mailbox, the record settles it without an argument, and without you absorbing the cost of a mistake you didn't make.
Questions to Settle Before You Switch It On
The technical setup for white label client access is short. The decisions around it are what determine whether it reduces your support load or increases it.
Which clients get access at all? Not every client wants it, and some will do more harm than good with it. Offering it selectively is entirely reasonable.
What can they break? A client who can delete mailboxes can delete a mailbox with mail in it. Decide whether the destructive actions belong in the role you're handing out, or whether those stay with you.
Who do they contact when stuck? Branded access means they'll contact you rather than us, which is the point — but only works if your support details are set on the brand profile, covered in domain branding.
What happens when the relationship ends? Removing a client's access shouldn't disturb their mail, and their staff shouldn't lose mailboxes because an administrator was removed. Know how that separation works before you need it, not during a difficult conversation.
The Price of the Add-On
White label client access extends the existing White Label Lite subscription — $39 a month or $389 a year — rather than introducing a separate charge. There's no per-client fee and no new plan tier, so the arithmetic doesn't change as you add clients.
That's the significant commercial difference from platforms that price reseller functionality per managed account. Your cost is flat; your revenue isn't. A reseller with forty clients pays the same as one with four, and the mailbox limits come from your underlying plan rather than from the branding add-on.
The subscription also carries 10% off current Drive prices while active, which matters if you're bundling storage into what you sell.
Whether This Is Worth Doing
White label client access isn't automatically right, and the honest version depends on the shape of your business.
If your clients rarely need changes, and you'd rather be the only person touching configuration, white label client access adds a surface to manage for little return. Plenty of small resellers are better served by keeping the dashboard to themselves and handling requests as they come.
It becomes compelling at the point where routine admin is consuming time you can't bill for, or where a client has asked for self-service and the alternative is losing them to a provider who offers it. That's usually somewhere between ten and thirty client domains, and the signal is your own inbox rather than any number on a page.
The underlying capability — clients administering their own domains under your brand, on your subscription — is the thing worth evaluating, because it changes what you can sell rather than only how it looks.
