> ## Documentation Index
> Fetch the complete documentation index at: https://docs.introw.io/llms.txt
> Use this file to discover all available pages before exploring further.

# 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.

> For partner ops putting the portal on a branded address partners trust.

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

<Steps>
  <Step title="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.
  </Step>

  <Step title="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.
  </Step>
</Steps>

## Steps

<Steps>
  <Step title="Open domain settings">
    Go to [Portal settings](https://app.introw.io/settings/portal) and open the custom domain configuration. If your plan does not include custom domains, you will be prompted to upgrade here.
  </Step>

  <Step title="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.
  </Step>

  <Step title="Create the DNS records at your provider">
    Introw generates the records you need; add each one exactly as shown at your DNS provider:

    * **Verification records** - confirm you own the hostname and let Introw issue the SSL certificate. Add them exactly so verification can complete.
    * **Mapping record** - points the hostname at the portal so traffic resolves to Introw. This is what makes the address actually load the portal.
  </Step>

  <Step title="Wait for propagation, then verify">
    DNS changes take time to propagate, sometimes minutes, sometimes longer depending on your provider. Once they resolve, verify the domain in Introw. On success, Introw issues a secure certificate automatically.
  </Step>

  <Step title="Confirm the portal loads">
    Visit your hostname and confirm the portal serves over a secure connection on your domain.
  </Step>
</Steps>

## 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.

## Related

<CardGroup cols={2}>
  <Card title="Remove a custom domain" icon="book-open" href="./remove-a-custom-domain">
    Disconnect a domain you no longer use.
  </Card>

  <Card title="Brand the partner portal" icon="book-open" href="/features/portal/branding/guides/brand-the-partner-portal">
    Match the brand to your new domain.
  </Card>

  <Card title="Implementation reference" icon="screwdriver-wrench" href="../technical">
    Full custom domain configuration options.
  </Card>
</CardGroup>