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

# Set up a branded portal domain

> Connect your domain using its generated DNS records and verify the customer entry point.

Combine workspace [branding](/v3/guides/accounts/branding) with a verified custom domain to give clients a branded portal address.

## Before you start

Have access to the workspace and to the DNS settings for your hostname. Decide which address clients should use, such as `ai.example.com`. Configure your logo and workspace name under **Branding**.

## Connect the domain

1. Open **Domain** in the workspace navigation and select **Add domain**.
2. Enter the hostname you intend to use. Follow the form's validation rather than pasting a full page URL.
3. Expand **DNS setup** for that hostname. Copy each displayed record's **Type**, **Name** and **Value** to your DNS provider. Use the full name when your provider requires it.
4. Use **Check DNS** to retrieve or refresh the setup records. Do not copy an IP address or CNAME from an old guide or another workspace.
5. After updating DNS, select **Verify connection**. DNS changes can take time to propagate; inspect the current status before changing records again.
6. Once the domain is connected, use its actions menu to make it the default if that is the intended workspace address.

## Domain fields and statuses

Enter a hostname such as `ai.example.com`: omit `https://`, paths, ports and wildcards. The form trims whitespace and converts it to lowercase.

| Display or control | Meaning |
| - | - |
| DNS record **Type** | The generated `CNAME`, `A`, or ownership `TXT` record; use the type shown for your domain |
| **Name** / **Full name** | Use the short name when your DNS provider appends the domain; use the full name when it does not. `@` represents the root. |
| **Value** | Exact generated destination or verification value to copy |
| **Check DNS** | Refreshes routing and ownership information; it does not edit your DNS provider |
| **Routing detected** / **Routing not detected** / **Routing status unavailable** | Whether the current check found supported routing, found none, or could not return routing status |
| **Ownership verified** / **Ownership pending** | Whether ownership verification has completed; this is separate from routing |
| **Verify connection** | Rechecks setup after you change DNS |
| **Setup pending** | The domain has not reached the connected state |
| **Needs attention** | Setup reported an error; inspect **Connection details** and the generated records |
| **Connected** | The saved domain is connected; still test HTTPS and sign-in |
| **Default** | The workspace's selected default domain |
| **SSL active** | The connected domain also reports SSL enabled |
| **Make default** | Available for a connected domain that is not already the default |
| **Remove domain** | Removes this portal-domain configuration after confirmation; update client links before removing an address they use |

Removing the portal configuration does not edit the DNS records at your registrar.

## Verify the customer experience

Open the address over HTTPS in a fresh browser session. Check the sign-in page, sign-in completion and intended client account. If installing the portal inside GHL, generate a new [custom menu link](/v3/guides/ghl/menu-link) with this verified domain and test it as a client.

If DNS records are unavailable, use **Check DNS**. If the service reports that the domain belongs to another hosting project, resolve that ownership or contact support. An ownership check and a fully configured domain are separate states; wait for the configured result.

This setup covers the portal address and supported branding fields. Review your actual customer journey before making promises about every email, integration or external service displaying your brand.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.