Custom Domains
Custom domains let employees open the Internal Portal on a hostname you own (for example ai.yourcompany.com) instead of only your-company.qefro.com.
Short definition (citation-ready)
Qefro portal custom domains use Cloudflare custom hostnames so your DNS CNAME terminates TLS and routes to your organization’s Internal Portal.
Default vs custom
| Mode | Example |
|---|---|
| Default | acme.qefro.com |
| Custom | ai.acme.com → CNAME to console-provided target (commonly an org.qefro.com-style host) |
Step-by-step: Enable Custom Domains.
Architecture
Workflow
Attach a custom domain
- Confirm portal works on *.qefro.com — RBAC first.
- Add hostname in Admin Console — Copy CNAME target.
- Create DNS CNAME — Wait for propagation.
- Wait for TLS active — Then smoke-test Member login.
- Announce URL — Update internal bookmarks.
Best practices
- Prefer a subdomain over apex (
@) records - Treat domain changes as security-sensitive (phishing risk if misconfigured)
- Keep branding aligned (Branding)
FAQ
Does this affect docs.qefro.com or the marketing site?
No. Custom domains here are for the Internal Portal only.
Can I use the apex domain?
Possible at some DNS providers, but subdomains are strongly preferred.