Skip to main content

Set Up SAML SSO

Connect your identity provider to Tomba so your team can sign in with SSO.

Written by Tomba.io Team

Connect your identity provider to Tomba so your team can sign in with their company login. An identity provider is the service your company uses to manage logins, such as Okta, Microsoft Entra ID or Google Workspace.

Before you start

  • A Tomba Enterprise plan.

  • The Owner or Admin role in your workspace.

  • Admin access to your identity provider. If you don't have it, ask your IT team.

💡 Tip: Using Google Workspace? Follow Set Up SSO with Google Workspace instead.

Add Tomba to your identity provider

  1. Under Service provider details, copy the Entity ID (Audience URI) and the ACS URL (Reply URL).

  2. In your identity provider's admin console, create a new custom SAML app.

  3. Paste both values into the app.

  4. Set the Name ID format to Email. This is how Tomba identifies your users.

  5. Save the app.

Upload the metadata to Tomba

Your identity provider gives you a metadata XML file for the new app. This small file tells Tomba to trust its sign-ins. Download it, then:

  1. On Settings > SAML SSO, click Configure SAML SSO.

  2. Choose Upload file and add the file, or choose Paste XML and paste its contents.

  3. Check the preview, which shows the Entity ID, SSO URL and Certificates.

  4. Click Save and enable SSO.

To change it later, click Replace metadata, then Update metadata.

Verify your email domain

Do this before you test. Tomba uses the domain in your email address to find your SSO login, so nobody can reach it until the domain is verified. Follow the steps in Verify Your Domain for SSO.

Test the sign-in

  1. Open a private browser window.

  2. Go to the Tomba sign-in page and click Sign in with SSO.

  3. Enter your Work email and click Continue.

  4. Click Continue with SSO.

  5. Sign in with your identity provider. You should then be signed in to Tomba.

Choose how your team signs in

Under Sign-in method, pick All methods, SSO preferred or Only SAML SSO. See SSO Enforcement Modes for what each one does.

Common questions

Why do I see "SSO not configured"?

Tomba can't match your email to an SSO setup. Check that your domain shows as verified under Verified domains, and that you're using an address on that domain.

Why does sign-in fail at my identity provider?

Check these three things in your identity provider:

  • The Entity ID and ACS URL match exactly what Tomba shows.

  • The Name ID format is Email.

  • The SAML app is turned on for your user.

Do new members need an invitation?

Not if Just-in-time provisioning is on. Tomba creates an account the first time someone signs in with SSO, and gives them the Default role shown on the same page.

Related articles

Did this answer your question?