On a white-label plan, your clients never have to see our name. You point a hostname of your own — panel.youragency.com — at our infrastructure, and the same control panel answers on it wearing your brand.
Nothing is installed on your side. There is no copy of anything, no server to keep, no software to update. One DNS record is the whole of what lives with you.
Open Agency Partners in the sidebar, then Panel domain.
What your clients can reach there
The panel and the doors into it: the sign-in page, the password pages, their services, their own account details, and our Terms and Privacy. That is the complete list.
Everything else — our catalogue, our prices, the cart, the checkout — answers 404 on your hostname. It is not redirected to us, because a redirect would put our address in your client's address bar, which is the one thing the option exists to prevent.
Note
There is no sign-up form on your hostname either. Accounts are made by you, one client at a time, from Clients.
Use a subdomain, not your domain itself
Ask for panel., client. or my. — a name in front of the domain you already use. Two reasons, and both matter:
- A domain on its own cannot carry the kind of DNS record we ask for, so it would have to point at a fixed address that changes when hosting does.
- Pointing your whole domain here would send your own website to our panel.
With a subdomain your website stays exactly where it is.
The five steps
The order is deliberate. Your DNS change is last, so no client of yours ever arrives before the hostname is ready.
- Claim it. Type the hostname on the Panel domain page and save. The page then shows you a verification record.
- Prove it is yours. At your registrar or DNS provider, publish the
TXTrecord exactly as the page prints it. It sits under a label beginning_digipacket-verify. - Check it. Come back and press Check the record. The state becomes Verified.
- Wait for us. Pressing Check the record tells our team straight away, with your hostname — you do not need to open a ticket. We then add the hostname to the server and let its certificate issue. This is a person doing two things by hand; it is not instant. The state becomes Live when it is done, and only then is the hostname ready.
While you wait, the page already shows you the
CNAMEyou will publish, so you can have it ready. Do not publish it yet. - Point it here. Once the state is Live, publish the
CNAMErecord the page shows you.
Important
Do not publish the CNAME before the state says Live. Until the hostname exists on our server, a client of yours who typed it would be shown our own website under your name, or a certificate warning naming us.
If your DNS is behind a proxy
If your DNS provider offers a proxy or CDN in front of records — an orange cloud, a "proxied" switch — leave it off for this record. A proxy terminates the encryption itself, and the certificate for your hostname cannot then be issued or renewed.
One hostname per agency
A second one immediately raises the question of which is the main one: which appears in your clients' invitation e-mails, which is the address in their password links. There is no answer to that you would want to be asked for, so there is one. If you are renaming, release the old hostname and claim the new one.