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

# Set Up a Custom Domain for Your LumiID Site

> Replace your default LumiID subdomain with your own domain like docs.yourcompany.com. Requires a paid plan and access to your DNS provider.

By default, your site is published at a subdomain of the LumiID platform. You can replace this with your own domain — for example, `docs.yourcompany.com` — so your documentation looks and feels like a natural part of your brand. Custom domains are available on any paid plan.

## Prerequisites

Before you begin, make sure you have:

* A paid plan (Pro or above)
* Access to your domain's DNS settings through your DNS provider
* A published LumiID site

## Setup steps

**1. Add your domain in settings**

Go to **Settings → Publishing → Custom domain** and enter the domain or subdomain you want to use (for example, `docs.yourcompany.com`). Click **Save**.

**2. Create a CNAME record**

In your DNS provider, create a CNAME record pointing your subdomain to the address shown in your LumiID settings. DNS changes can take up to 48 hours to propagate, though it usually happens much faster.

```txt theme={null}
Type:  CNAME
Name:  docs
Value: sites.example-platform.com
```

**3. Verify and activate**

Return to **Settings → Publishing → Custom domain** and click **Verify**. Once LumiID confirms the DNS record is in place, your SSL certificate is provisioned automatically — this usually takes just a few minutes.

> [!NOTE]
>
> If you're using an apex domain (for example, `yourcompany.com` without a subdomain), you'll need to set an ALIAS or ANAME record instead of a CNAME. Not all DNS providers support this — check your provider's documentation before proceeding.

## Troubleshooting

> [accordion] Verification keeps failing
>
> Make sure there are no conflicting DNS records for the same subdomain. An existing A record pointing to another address will block the CNAME from resolving correctly. Remove or update the conflicting record in your DNS provider, then try verifying again.

> [accordion] SSL certificate not provisioning
>
> SSL is issued automatically after DNS verification. If your certificate hasn't appeared after 30 minutes, try clicking **Verify** again in **Settings → Publishing → Custom domain** to trigger a fresh check.

> [accordion] Site loads but shows an SSL warning
>
> This usually means your browser has cached an old or expired certificate. Try clearing your browser cache and reloading the page, or wait a few more minutes for propagation to complete.


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