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

# Connect a custom domain

> Put your public portal on a customer-owned hostname such as feedback.example.com.

Use a custom domain when you want customers to visit your portal from a hostname you own, such as `feedback.example.com`.

## Requirements

* You must be a workspace owner or admin.
* Your workspace must be on a paid plan (Starter, Growth, or Plus).
* You can connect one custom domain per workspace.
* The hostname cannot already be connected to another workspace.

Use a subdomain such as `feedback.example.com` or `updates.example.com` unless your DNS setup specifically supports the records shown in the dashboard.

## Add a domain

Open **Workspace settings → Domain**, choose **Add domain**, and enter the exact hostname you want customers to use.

```text theme={null}
feedback.example.com
```

Glean Feed checks the hostname and shows the DNS records you need to add at your DNS provider.

## DNS and SSL

For subdomains, add the CNAME record shown in the dashboard. The value may look like this:

```text theme={null}
cname.vercel-dns.com
```

If ownership verification is required, the dashboard also shows TXT records. Add every required record before you refresh status.

Glean Feed provisions SSL after DNS resolves and verification succeeds.

## Check status

A domain is active only when both domain status and SSL status are active. Pending domains show the records that still need to resolve.

DNS changes can take time to propagate. Use the refresh action in the dashboard after you add or correct records.

<Check>
  The custom hostname is ready only when the dashboard shows both domain and SSL status as active.
  Open the hostname in a private browser window and confirm it loads the correct workspace portal.
</Check>

## Switching domains

Remove the current domain before adding a different hostname. This keeps the workspace tied to one public custom domain at a time.

If removal fails, the domain stays connected to this workspace so the hostname cannot be claimed while cleanup is incomplete. Try removing it again after a minute. If it keeps failing, contact support before adding the hostname to another workspace.