Documentation › Configure
Custom domains
Serve any branch on your own domain: the DNS record to create, and automatic HTTPS.
Add the domain In the project's Settings → Custom domains , enter the host, for example erp.yourcompany.com , pick the branch it serves and click Add domain . Or add it from a branch's Settings tab, under Custom domains , for that branch.
Create the DNS record At your DNS provider, create the record shown next to the domain.
Click Check Click Check next to the domain. The status goes from Waiting for DNS to Waiting for certificate to Active . The domain follows new builds of the branch without any rebuild.
DNS records
Domain Type Value erp.yourcompany.com CNAME <project>.cloud.knovadigital.com yourcompany.com A the server's IP address, shown next to the domain
A subdomain ( erp. , www. …) uses a CNAME . A bare domain can't have a CNAME, so it uses an A record.
With Cloudflare, set the record to DNS only (grey cloud), not proxied.
DNS changes can take from a few minutes to a few hours to be visible. Click Check again later.
HTTPS
As soon as the DNS points to the platform, a free Let's Encrypt certificate is requested for the domain, usually within a few minutes, and renewed automatically. There is nothing to upload.
Primary domain and extra addresses
Make a production domain the primary one from its ⋯ menu ( Make it the primary address ; admins): it gets a Primary badge and becomes Odoo's web.base.url , used in emails and links.
An address like name.cloud.knovadigital.com needs no DNS record at all: the platform already covers it.
Once your domain works, Settings → Name & address can block the default cloud.knovadigital.com address of production ( Block access to the … address for production ), so search engines only see one address.
Admins manage production domains, testers staging domains and developers development domains.