Integrations > Authentication and SSO
Domain verification
Prove you own your email domain
Section titled “Prove you own your email domain”Domain verification tells Tallyfy that an email domain like acme.com really belongs to your organization. You prove it by adding one DNS TXT record. Once a domain is verified, Tallyfy can safely auto-join new people from that domain and let you enforce SSO-only login. You do all of this yourself under Settings > Organization > Security > Domains, on any paid plan.
Why it matters: SSO assertions carry an email address, but an email address alone isn’t proof. Any identity provider can technically assert any email. A verified domain is the check that stops someone whose own IdP claims an @acme.com address from being auto-added to your Acme org.
What a verified domain turns on
Section titled “What a verified domain turns on”A domain stays unverified until you publish the TXT record. Verifying it turns on two things:
| Feature | What verification enables |
|---|---|
| Auto-join (JIT) | New users whose email is on a verified domain get a Tallyfy account created automatically on first SSO login (when auto-join is on). |
| SSO-only enforcement | The Require SSO switch stays disabled until you have a verified domain, because enforcement without proof of ownership is unsafe. |
Plain SSO login works without a verified domain. You only need verification for auto-join and enforcement.
Add and verify a domain
Section titled “Add and verify a domain”You’ll need access to your domain’s DNS settings (or someone on your team who has it). The record is a standard TXT entry, the same kind you’d add for email or other service verifications.
- In Tallyfy, go to Settings > Organization > Security > Domains.
- Click Add domain and enter your domain, for example
acme.com. Use the bare domain, not a full email address. - Tallyfy shows you a TXT record name and a unique value to publish. Copy both with the copy buttons.
- In your DNS provider (GoDaddy, Cloudflare, Route 53, and so on), add a new TXT record using that name and value. Save it.
- Back in Tallyfy, click Verify. Tallyfy looks up the TXT record and, once it matches, marks the domain verified with a badge.
DNS changes can take a few minutes to propagate, sometimes longer. If the first verify attempt fails, wait a bit and try again. The token stays valid, so you don’t need to start over.
After verification
Section titled “After verification”Once the badge shows verified, you can keep the TXT record in place. Tallyfy may re-check ownership over time, so removing the record later can un-verify the domain.
Add every domain your team uses for email. If people sign in from both acme.com and acme.co.uk, verify both so auto-join and enforcement cover everyone.
Troubleshooting
Section titled “Troubleshooting”Verification not passing? Check these:
- The TXT record name and value match exactly what Tallyfy shows. A trailing space or a missing character will fail.
- You added a TXT record, not a CNAME or A record.
- You’re verifying the bare domain (
acme.com), not a subdomain or an email address. - Enough time has passed for DNS to propagate. Try again after a few minutes.
- You can confirm the record is live with a public DNS lookup tool before clicking Verify again.
Related articles
Section titled “Related articles”Authentication > SSO enforcement and break-glass
Authentication > Integrate JumpCloud SSO
Authentication > Integrate OneLogin SSO
Was this helpful?
- 2026 Tallyfy, Inc.
- Privacy Policy
- Terms of Use
- Report Issue
- Trademarks