Add A Custom Domain
Attach a branded domain to your workspace.
Custom domains let customers use a branded host instead of only the built-in workspace subdomain.
Use a subdomain such as portal.example.com or app.example.com. Avoid using
your root marketing domain unless your DNS and website setup are intentionally
designed for that.
Plan the hostname before customers receive public links. Changing domains later means updating links in emails, invoices, estimates, forms, booking pages, storefronts, and saved documents.
Choose the Right Hostname
Use a dedicated subdomain that is not already serving another app. Common choices are:
portal.example.comapp.example.comclients.example.combooking.example.com
Do not point a hostname at Agiled if it already hosts your website, email tracking, help center, or another customer portal.
Add The Domain
- Open Settings.
- Go to Domains.
- Enter the custom domain, such as
portal.brand.com. - Select Save domain.
- Copy the DNS records shown by Agiled.
- Add those records at your DNS provider.
- Return to Agiled and verify DNS.
The built-in workspace subdomain remains available even when a custom domain is configured.
Keep the built-in subdomain as a fallback while DNS is being verified. Do not remove or replace public links in campaigns until the custom domain opens successfully in a private browser window.
Add DNS Records
Open your DNS provider and create the exact records Agiled shows. Copy the host, record type, and value without changing punctuation or adding the full domain twice.
If your DNS provider has a proxy option, start with DNS-only mode unless Agiled or the provider instructions say otherwise. Proxied records can hide the real target during verification.
Who Can Manage Domains
Domain changes are limited to owners and admins. If the domain fields are disabled, ask an owner or admin to make the change.
Before Sharing The Domain
Wait for DNS verification to pass, then test customer-facing links in a private browser window. Check booking pages, public forms, invoices, estimates, documents, storefronts, and checkout links that should use the branded domain.
DNS Troubleshooting
If verification fails, confirm the record type, host/name, value, proxy status, and TTL at your DNS provider. DNS changes can take time to propagate. If another service already uses the same hostname, choose a different subdomain or update that service first.
If your provider automatically appends the root domain, enter only the subdomain
part in the host field. For example, enter portal, not portal.example.com,
when the provider already shows .example.com beside the field.
If the domain verifies but links still show the workspace subdomain, refresh the app and regenerate or resend the customer-facing link from the correct workspace.
Launch Checklist
Before announcing the branded domain:
- Confirm DNS verification passes.
- Open the domain in a private browser.
- Test at least one booking page, form, document, invoice, and checkout link.
- Confirm links use HTTPS.
- Update website buttons, email templates, and saved public links.
- Keep the old links available until customers have received the new domain.
Security Notes
Only add domains you control. Removing DNS later does not automatically revoke links already sent to customers, so update public links if you move the customer experience to a different hostname.