Skip to main content
A custom domain makes the portal’s URL yours, which builds partner trust and reinforces your brand. This guide takes the whole job end to end: add your hostname, create the DNS records Introw generates at your provider, and verify so Introw issues a secure certificate and the portal serves on your domain. Until you finish, the portal stays on its default subdomain, so partners are never locked out.

​
What you’ll achieve

A verified custom domain serving the partner portal securely on your own hostname, with a certificate issued automatically, so partners reach the portal at an address that looks like yours.

​
Before you start

1

Confirm the plan and access

Custom domains are a plan feature; if your plan does not include them you will be prompted to upgrade. You also need admin access to portal settings. Check what your plan includes at introw.io/pricing.
2

Have a hostname and DNS access

Choose a hostname you control, such as partners.yourcompany.com, and make sure you can add records at your DNS provider.

​
Steps

1

Open domain settings

Go to Portal settings and open the custom domain configuration. If your plan does not include custom domains, you will be prompted to upgrade here.
2

Enter your hostname

Add the domain you want the portal served on, such as partners.yourcompany.com. Use a subdomain you control and are not already using elsewhere, so it can point cleanly at the portal.
3

Create the CNAME record at your provider

There is exactly one record to add, and Introw shows both halves of it with a copy button:
  • CNAME name - the hostname you entered, for example partners.yourcompany.com.
  • CNAME value - your organisation’s target on cname.introw.io.
Because it is a CNAME, the hostname has to be a subdomain: a root domain like yourcompany.com cannot take one. There is no TXT record to add and no token to keep in sync - ownership is proven over HTTP once the CNAME resolves, which is why nothing here expires while you wait for your provider.
4

Wait for propagation, then sync the status

DNS changes take time to propagate, sometimes minutes, sometimes longer depending on your provider. Use Sync status in the dialog to re-check: it tells you which half of the job is outstanding - CNAME not detected means the record has not resolved yet, while an SSL state means the record is right and the certificate is still being issued. The certificate is issued automatically, at TLS 1.3, and renews itself.
5

Confirm the portal loads

Visit your hostname and confirm the portal serves over a secure connection on your domain.

​
Verify it worked

The domain shows as verified in settings, the portal loads on your hostname with a secure certificate, and the default subdomain no longer needs to be shared with partners. If it stays pending, re-run Sync status: CNAME not detected points at the DNS record, anything else points at certificate issuance.

Remove a custom domain

Disconnect a domain you no longer use.

Brand the partner portal

Match the brand to your new domain.

Implementation reference

Full custom domain configuration options.