Skip to content
OpenPartner docs

White-label setup

The white-label add-on serves your entire partner portal from your own domain (partners.yourbrand.com), with your branding only: no OpenPartner logo or name anywhere your partners look, emails from your own address, and your program kept off the shared Network marketplace entirely.

This page is the full setup, in order. Budget an afternoon end to end — most of it is waiting for DNS.

Before you start

You need an active plan subscription (Flex or RevShare). If you haven’t subscribed yet, don’t detour to Billing — step 1’s button bundles the plan and the add-on into a single checkout.

You’ll also need access to your domain’s DNS (wherever you manage records for yourbrand.com) and, for step 4, the SMTP details of a mailbox you own.

1. Enable the add-on

In your dashboard: White label (left sidebar) →

  • Already subscribed? Click Enable white-label add-on. It’s added to your existing subscription as a prorated monthly line item — no new checkout, and it appears on your next invoice.
  • Not subscribed yet? The button reads Subscribe with white-label included and opens one Stripe checkout carrying both your plan and the add-on. If you have a promotion code, there’s a field for it at checkout.

The moment the add-on is active, platform branding disappears from your portal, Network surfaces are hidden, and (if you were listed) your marketplace listings are withdrawn. The Custom domain section unlocks below the add-on card.

2. Connect your domain

Use a subdomain you own — partners.yourbrand.com or portal.yourbrand.com (apex domains like yourbrand.com aren’t supported). In White label → Custom domain:

  1. Enter the subdomain and click Register. You’ll get two DNS records, each with a copy button: a CNAME (points your subdomain at our edge) and a TXT record (proves you own the domain).
  2. Add both records wherever you manage DNS.
  3. Once they’ve propagated — usually minutes, occasionally up to an hour — click Verify. If it reports the records aren’t visible yet, just wait and retry; the values don’t change.
  4. On success, your TLS certificate is provisioned automatically. The domain is typically live within ~15 minutes: open https://partners.yourbrand.com and you should see your sign-in page.

The TXT record is permanent. It’s your ongoing proof of ownership, re-checked daily — if it’s ever removed, the domain is automatically disabled until you verify again.

From verification onward, everything moves to your domain: the portal itself, partner sign-in links in emails, and your public partner application page.

3. Brand the portal

Settings → Brand info: set your brand name (shown everywhere partners look), upload your logo, and pick your accent color. With white-label active there is no fallback to platform branding — if you skip the logo, partners see a neutral monogram of your brand name, never anyone else’s mark.

4. Send email from your own address

By default, transactional email (sign-in links, partner invites) is delivered by the platform’s shared sender. To send from your own domain instead — recommended for white-label — go to Settings → Email delivery:

  1. Provider: SMTP (or Postmark, if that’s what you use).
  2. Enter the SMTP host, port, and mailbox credentials from your email provider — the exact hostname matters (e.g. Namecheap Private Email is mail.privateemail.com, not mail.yourbrand.com).
  3. Port 465 → check the SSL/TLS box; port 587 → leave it unchecked.
  4. Save, then click Send test email — it delivers a test message to your admin inbox and shows the exact transport error if something’s wrong.

Because mail goes out through your own provider, your existing SPF/DKIM records apply — there’s nothing to configure on the OpenPartner side. If you haven’t set those up, your email provider’s dashboard lists the records (they’re theirs to issue, not ours).

5. Open (or curate) partner signups

Your portal has a public application page at https://partners.yourbrand.com/join. Control it under Settings → Partner signups:

  • Accept public applications — on: anyone with the link can apply. Off: the page shows “signups closed” and partners join by invite only.
  • When someone applies — approve automatically (they can sign in right away) or hold every application for your review.

Direct invites from Admin → Partners always work regardless of this setting.

6. Wire up tracking on your site

Follow Integrate your site — the SDK snippet, the identify() call, and server-side revenue events. One white-label specific detail: use your own domain as the API base everywhere —

OpenPartner.init({ apiUrl: 'https://partners.yourbrand.com/api' });

— so nothing in your site’s network traffic references the platform either.

7. Test, then invite

Run the end-to-end test loop with one test partner: click their link, sign up, fire a test event, watch the commission land. Confirm the sign-in email arrives from your address and links to your domain. Then invite real partners — or share your /join page.

Good to know

  • Billing — the add-on bills monthly alongside your plan. Disabling it removes the line item with a prorated credit, returns the portal to platform branding, and stops your custom domain from resolving.
  • If your subscription lapses, the portal degrades gracefully: sign-in keeps working on your domain while platform branding returns, and the domain is disabled shortly after. Restore billing and re-verify to bring it back — your domain registration and history are kept.
  • Sessions are per-domain by design: signing in at partners.yourbrand.com doesn’t sign you in at app.openpartner.dev, and vice versa. Your workspace remains reachable from both; your partners only ever see your domain.
  • Your partners are yours alone. White-label workspaces are fully isolated from the shared Network — your program isn’t discoverable, and your roster is never shared.