Skip to main content
Open in Introw: Portal settings

​
How it works

You add the hostname you want the portal served on, and Introw gives you the DNS records to add at your domain provider. Once those records propagate and verify, Introw issues a secure certificate and the portal becomes reachable on your domain. Until a domain is verified, the portal is served on a default subdomain. A domain must be unlocked for partners to access the portal: that means either using the default subdomain or completing custom domain verification. Custom domains are a plan feature, so an org on a plan without them is prompted to upgrade when adding one.

​
Prerequisites

  • A plan that includes custom domains.
  • Admin access to portal settings.
  • Access to your DNS provider to add records.
  • A hostname you control, such as partners.yourcompany.com.

​
Settings & configuration

Custom domains are configured from Portal settings.

​
Adding a domain

Enter the hostname you want to use for the portal. Introw generates the DNS records you need to add to make the domain point at the portal and prove you own it.

​
DNS records

Add the records Introw shows to your DNS provider. These typically include records that point the hostname to Introw and records that verify ownership. DNS changes can take time to propagate before verification succeeds.

​
Verification and certificate

Once the records resolve, Introw verifies the domain and issues a secure certificate automatically. The portal then serves on your domain.

​
Removing a domain

You can remove a custom domain to stop serving the portal there; the portal falls back to the default subdomain.

​
Setup walkthrough

1

Open domain settings

Go to Portal settings and open the custom domain configuration.
2

Add your hostname

Enter the domain you want the portal served on.
3

Add DNS records

Copy the provided records into your DNS provider.
4

Verify

Wait for DNS to propagate, then verify the domain.
5

Confirm

Visit the domain to confirm the portal serves securely.

​
How-to guides

Connect a custom domain

Add your hostname, create the DNS records it generates, and verify so the partner portal serves securely on your own domain.

Remove a custom domain

Disconnect a custom domain so the portal falls back to its default address without locking partners out.

​
Limits & gotchas

DNS changes can take time to propagate, so verification may not succeed immediately. The portal only serves on a custom domain after verification; until then it stays on the default subdomain. Removing a domain takes the portal off that hostname.

​
Troubleshooting

  • Verification keeps failing - the DNS records have not propagated yet or were entered incorrectly.
  • The portal is still on the subdomain - the custom domain is not verified yet.
  • The certificate is not secure - verification has not completed, so no certificate has been issued.