Verify a Domain for SSO
Claim a domain in the Developer Console, publish its DNS TXT record, verify it for use across SSO connections, and remove it.
Claim and verify a domain
In the Developer Console, Tenant → Domains holds the Account's verified email domains for admin SSO: people whose email ends in a verified domain are routed to the Account's admin connection. An organization's end-user SSO domains are claimed on the organization instead, in the Domains section of its Policy tab, with the same claim, TXT record, and verify steps; the record name there is _sso-verification.<domain>. Domains are a Pro feature; on a Free account the page says so and offers no Add domain.
- Application
- Developer Console
- Path
- TenantDomains
- Opens with
sso.viewRead SSO connections, verified domains, the custom auth domain, and directory sync.
- Context
- Account-wide. No Application or Environment selection applies.
Claim and verify a domain
acme.com. A pasted URL is trimmed to its host, so https://acme.com/login becomes acme.com; what remains must be a domain name, or the dialog refuses it inline with Enter a domain like acme.com, without https:// or a path. A public email provider's domain such as gmail.com is refused too, since nobody can prove ownership of it._canopy-verification.<domain>), a DNS record value, and a Verify action.If you don't see this
Each control on the Domains page exists only for someone who may use it. When something described above is missing, one of these is why:
Tell us how we can improve this guide.