Custom Domains: What, Why, When, and How
The complete guide to serving Allsorts CRM at your own domain instead of the shared one.
What a custom domain is
Normally your team accesses the CRM at the shared Allsorts CRM address. A custom domain lets you instead serve it at your own address — for example `crm.yourbusiness.co.za` — so the login page, dashboard, and everything else your team sees loads under a domain you control.
Why you'd want one
Two reasons, in practice: it looks more professional to your own team and any client-facing pages when the address matches your business, and it's the foundation for white-labeling (replacing "Allsorts CRM" with your own app name — see White-Labeling Your CRM). It's a small but real trust signal, especially if staff are logging in daily.
When to set it up
Once your business branding is already configured (see Setting Up Your Business Branding) and you're on a plan that includes it — this isn't a day-one step for most teams, but worth doing once you're committed to the system.
Who has access
Custom domains are included on the Growth and Scale plans. They're also unlocked for everyone during the 14-day trial, so you can test the setup before deciding on a plan. Starter does not include this feature — see Understanding Plans and Pricing.
How to set it up
- Go to Settings → Domain.
- Enter your domain (e.g. `crm.yourbusiness.co.za`) and save.
- Add the CNAME DNS record shown on that page, pointing your domain at the CRM's canonical host — this is done in your own domain registrar or DNS provider (e.g. Cloudflare), not inside the CRM.
- Click Verify — the system performs a real DNS lookup to confirm the CNAME is correctly pointed before marking your domain as active. DNS changes can take a few minutes to a few hours to propagate, so a failed first attempt right after adding the record usually just means "not yet" rather than something being wrong.
- Once verified, your domain serves the CRM with your team's branding automatically.
One important limitation: this system doesn't issue SSL certificates itself. For your domain to work over HTTPS, it needs to sit behind a reverse proxy or CDN that handles TLS — Cloudflare is the common choice. Talk to whoever manages your DNS/hosting if you're not sure how to set that part up.