Configure a Custom Portal Domain
Point a member-facing domain such as members.yourgym.com at your Topo portal and verify DNS/TLS status.
What the portal domain is
The portal domain is the web address members use for your Topo member portal, including sign-in, account pages, events, and signup links. It is separate from the email sender domain used for outgoing email.
Before you start
Choose a subdomain you control, such as members.yourgym.com or portal.yourgym.com.
Make sure you can edit DNS records with your DNS provider.
Avoid using your main website root unless you intentionally want the whole domain to point at Topo. A subdomain is usually safer.
Add the domain
Go to Staff > Account > Custom domain.
In Portal domain, enter the domain members should visit.
Choose Add domain and confirm.
Copy the CNAME record Topo shows.
Add that CNAME at your DNS provider exactly as shown.
Return to Topo and choose Re-check.
Understand statuses
Pending means Topo is waiting for DNS propagation or certificate provisioning.
DNS verified means the DNS record can be seen, but the secure certificate may still be finishing.
Active means traffic to the custom domain routes to your member portal.
Unreachable or failed means Topo cannot see the expected DNS record. Double-check the host and value, then re-check.
After the domain is active
Your default Topo slug URL continues to work.
Members using the new domain may need to sign in again because the browser treats it as a different site. Their accounts and history do not change.
Update website links, QR codes, email templates, and staff scripts to use the new portal domain when ready.
If you remove the domain, members should return to the default Topo slug URL.
Common issues and fixes
The domain is not verified: make sure you added a CNAME, not an A record, unless your DNS provider is intentionally flattening it.
The DNS host is wrong: some DNS providers want only the subdomain label, while others want the full domain. Match your provider's convention but keep the final resolved record the same.
The domain works without HTTPS but not securely: wait a few minutes and re-check; certificate provisioning can lag behind DNS.
You need someone technical to add DNS: use the send-instructions option when available to email the records to your domain administrator.