Skip to content

Portal Domain

Your portal can be reached at two kinds of address, both managed from the Portal Domain card under Portal Setup → Other:

  • Subdomain — your always-on base address, your-subdomain.partnerportal.io.
  • Custom Domain — an optional branded address (e.g. partners.your-company.com) that works in addition to your subdomain.

These are not either/or: your subdomain always works, and a custom domain is added on top of it.

Your subdomain is the default address partners use to reach your portal — for example acme.partnerportal.io. Every portal always has one, and it keeps working even if you add a custom domain.

  1. Open Portal Setup → Other and find the Portal Domain card.

  2. In the Subdomain section, click Edit.

  3. Enter the new subdomain. It must be lowercase, start with a letter, and can’t end in a dash. It also has to be unique across PartnerPortal.

  4. Click Save and confirm when prompted.

A custom domain lets partners reach your portal at your own branded address — e.g. partners.your-company.com — served alongside your your-subdomain.partnerportal.io address. Both remain live and both can be used to sign in.

  • A plan that includes custom domains.
  • A subdomain you control — e.g. partners.your-company.com. Use a subdomain, not your bare root domain (your-company.com).
  • Access to your DNS provider so you can add a CNAME record.

You set a custom domain up in two places, in this order:

  1. In your DNS, point the domain at PartnerPortal with a CNAME record. This secures the domain (TLS) and routes visitors to your portal.
  2. In PartnerPortal, enter the domain so we can finish configuring your portal — including sign-in — for that address.

Doing the DNS step first means the domain is ready to serve traffic the moment PartnerPortal finishes setting it up.

  1. Choose your domain, e.g. partners.your-company.com.

  2. Add a CNAME record in your DNS provider for that domain pointing to:

    ssl.partnerportal.io
  3. Wait for DNS to propagate. This can take from a few minutes to a few hours, depending on your provider.

  4. Enter the domain in PartnerPortal. In the Portal Domain card, open the Custom Domain section, click Edit, and enter your domain.

  5. Confirm and save. PartnerPortal finishes configuring your portal for the new domain — this can take up to a minute.

  6. Sign in again when redirected to the sign-in page.

  • Both your-subdomain.partnerportal.io and your custom domain work, and both can be used to sign in.
  • New certificates and DNS changes can take a little time to fully propagate. If the custom domain doesn’t load immediately, wait a few minutes and try again.

Open the Custom Domain section, click Edit, clear the domain field, and save. Confirm when prompted. Your portal will then be reachable only at your your-subdomain.partnerportal.io address, and you’ll be signed out and asked to sign in again. You can also remove the CNAME record from your DNS afterward.

Will my partnerportal.io address stop working if I add a custom domain?

Section titled “Will my partnerportal.io address stop working if I add a custom domain?”

No. A custom domain is added alongside your your-subdomain.partnerportal.io address. Both remain live, and the partnerportal.io address is always available as a fallback.

Can I use my root domain (like your-company.com)?

Section titled “Can I use my root domain (like your-company.com)?”

Use a subdomain such as partners.your-company.com. Root domains generally can’t use CNAME records and aren’t supported here.

Changing either the subdomain or the custom domain updates your portal’s sign-in configuration, so you need to sign in again once it completes. This is expected.

The custom domain isn’t loading yet — what should I check?

Section titled “The custom domain isn’t loading yet — what should I check?”

Confirm your CNAME points to ssl.partnerportal.io and that DNS has had time to propagate. If it still doesn’t load after propagation, contact [email protected].