User
Custom Domain
Create or review AI output for this feature.
Step-by-step guide
Before you start
Use the account and workspace that own the records. This page does not include administrator configuration forms.
Open this feature
Open /portal/qr-codes/domains on your application domain. The tasks below name the controls to use after opening the page.
Steps
You need control of the domain’s DNS and a plan that includes custom domains. Use the application’s displayed routing host and verification token; the docs do not supply a shared token.
Add and verify a domain
- Open Custom Domains in the intended workspace.
- In Domain, enter a hostname you control, for example go.yourbrand.com, then select Add domain.
- Read the DNS instructions displayed by the application. Copy the routing target and generated TXT verification token for this specific domain.
- At your DNS provider, add the records shown for your root domain or subdomain. Use the displayed values, not the example hostname in this guide.
- After DNS changes have propagated, return to this domain row and select Verify DNS.
- Check the verification status and the separate TXT, CNAME and SSL health indicators.
- If the domain is verified and should be the workspace default, select Set default. Check the Default state and open a test public link using the domain.
Fields shown in the interface
| Field or setting | What to enter or choose |
|---|---|
| Domain | A hostname you control, without a page path. The source normalizes the hostname and rejects duplicates. |
| TXT verification token | Use the value generated for this domain and the record name shown by the application. |
| CNAME / routing target | Use the routing host shown on this installation. DNS record names depend on root versus subdomain setup. |
| Set default | Available for a verified domain. Select only when this should become the workspace default. |
| SSL health | Check separately from TXT ownership verification; a verified token alone does not prove HTTPS works. |
Check the result
- The domain row is verified and its intended default state is correct.
- A public test link resolves through the expected hostname with working HTTPS. This external check has not been performed by this documentation update.
Problems and validation
| Problem | What to do |
|---|---|
| TXT record not found yet | Check record name and token at your DNS provider, wait for propagation and select Verify DNS again. |
| This domain already exists | Check the existing domain entry instead of creating a duplicate. |
| Plan does not include custom domains | Ask the workspace owner to review the plan and domain allowance. |
| Verified but public link fails | Check routing and SSL health; TXT verification checks ownership separately from routing. |
Technical reference
Sources for these task instructions
Role-scoped source references
Pinned commit: 5af0236c6d99c50079f5ab8b8fb035506634bd8d
Source-only route information
| Method | Source-default route |
|---|---|
| GET | /portal/qr-codes/domains |
| GET | /portal/brand/custom-domains |