Custom domains
Business and aboveA custom domain lets your organization serve Scopingly from a hostname you control — for example app.acme.com — instead of the default app.scopingly.io. The hostname maps to your tenant, with automatic TLS and a DNS-based ownership lifecycle.
What a custom domain is (and isn't)
A custom domain is a vanity hostname mapped to your organization for serving the app. It is distinct from SSO email-domain mapping, which decides which org an email address belongs to. A custom hostname decides which org an HTTP request is serving. These are two separate trust decisions and are configured separately.
The resolved hostname is routing context, not identity
Your organization is always determined from the signed-in user's verified session — never from the hostname alone. The custom domain routes the request; authorization still comes from the token. A mismatch fails closed.
The lifecycle
Adding a custom domain moves through a DNS/TLS state machine, from pending to active:
- Add the domain. An org admin registers the hostname in the Custom Domains section of Admin settings.
- Prove ownership. Scopingly issues a DNS TXT verification token. You add the TXT record to your DNS provider to prove you control the domain. (Only a hash of the token is stored server-side, and a fresh proof is required.)
- Point the hostname. You add a CNAME so the hostname routes to Scopingly's edge target.
- Verification. Scopingly checks the TXT proof and DNS setup. Once it passes, the managed edge provider issues and renews TLS for you — you never handle certificates.
- Active. The domain serves your tenant.
If verification doesn't succeed the first time, retry and diagnostics are available in the Custom Domains section to show what's outstanding (for example, a TXT record that hasn't propagated yet).
Who manages it
Custom domains are managed by org admins. Beyond the Business+ entitlement, the feature is also gated by a per-org rollout cohort — a platform app admin enables an organization for custom domains before the section becomes usable. If your org is entitled by plan but the controls are not yet available, it is awaiting cohort enablement.
Deactivation
Removing a custom domain is available for teardown. When a domain is removed, Scopingly records a permanent tombstone for the hostname so it can't be re-claimed by another tenant without a fresh ownership proof — closing the domain-takeover risk.
Scope of the MVP
One custom subdomain per organization is supported. Apex domains, wildcards, customer-uploaded certificates, and multiple domains per tenant are not part of the current release.