Verify your company's email domain so your team can sign in to Tomba with single sign-on (SSO). Your email domain is the part after @ in your team's addresses. Without a verified domain, members have no way to reach your SSO login.
Before you start
You need a Tomba Enterprise plan and the Owner or Admin role.
You also need to add a record to your domain's DNS settings. DNS is the system that controls how your domain works online. A TXT record is a short line of text you add there, which proves you own the domain.
💡 Tip: If you don't manage your company's domain, ask your IT team. Send them the three values from Step 2.
Step 1: Add your domain
Open Settings > SAML SSO.
Find Verified domains and click Add domain.
Type your email domain. If your team uses
@tomba.io, entertomba.io.Click Add domain.
Step 2: Add the TXT record
Tomba shows you the record to create. Use the copy buttons to avoid typos.
Field | Example |
Host / Name |
|
Type |
|
Value |
|
Add the record wherever your domain's DNS is managed, such as Cloudflare, GoDaddy or Namecheap.
Step 3: Wait for the check
Tomba looks for the record by itself. You'll see Checking DNS every 15 seconds… in the window.
If it works: You'll see Domain verified, and the window closes by itself.
If you see Still pending: DNS changes can take a while. Click Check again, or click I'll verify later and come back to it.
Manage your domains
Your domains stay listed under Verified domains:
Verified: The domain is ready for SSO.
Waiting for DNS verification: Tomba hasn't found the record yet. Click Verify to check again.
To remove a domain, click the trash icon, then confirm in the Remove domain? window. People with emails on that domain won't be matched to your SSO anymore.
Common questions
When do I need to do this?
Do it before you test an SSO sign-in, and before you turn on Only SAML SSO. That option stays off until a domain is verified.
Can I add more than one domain?
Yes. Add each email domain your team uses, and verify each one the same way.
Does this force my team to use SSO?
No. Verifying a domain only makes SSO available. You choose whether it's required in SSO Enforcement Modes.
Related articles
