Custom Domain

A custom domain lets your organization access TraceUnified under your own web address rather than a shared one — so the platform looks and feels like part of your own environment, and your users sign in somewhere that reads as yours.

A custom domain matters more for a regulated tool than it might for a consumer app, because your users are being trained to sign in somewhere and trust it with controlled data. An address on your own domain is a phishing defense as much as a branding choice: people learn to expect your URL, so a lookalike login page is easier to spot. The DNS verification step exists for the same security reason — it proves you actually control the domain before the platform will serve your workspace under it.

Setting it up

You configure your domain by adding a CNAME record in your DNS that points to TraceUnified, then verify it from the portal. Verification confirms you control the domain before it’s activated, which is what stops anyone pointing a domain they don’t own at your workspace. Once verified, an SSL certificate is provisioned automatically, so the custom domain is served securely over HTTPS without you having to manage certificates yourself.

Managing the domain

The portal shows your domain’s status through setup and verification, and you can remove the custom domain if you need to revert to the default address. Because the certificate is handled for you, ongoing maintenance — renewal in particular — isn’t something you have to track.

Why it matters

A custom domain is partly branding and partly trust: users recognize and trust an address on your own domain, and it keeps the platform consistent with the rest of your tooling. It works alongside your organization settings and single sign-on to make the platform feel like a native part of your environment.