Skip to main content

Set Up SSO with Google Workspace

Connect Google Workspace to Tomba so your team can sign in with their Google accounts.

Written by Tomba.io Team

Connect Google Workspace to Tomba so your team can sign in with the Google accounts they already use. Google Workspace acts as your identity provider, which is the service that manages your company's logins.

Before you start

You need:

  • A Tomba Enterprise plan

  • The Owner or Admin role in your Tomba workspace

  • Super administrator access to your Google Workspace

If you don't manage Google Workspace yourself, ask your IT team to do these steps with you.

Step 1: Add the app in Google Admin

  1. Open Apps > Web and mobile apps.

  2. Click Add app > Add custom SAML app.

  3. Enter an app name, such as Tomba.

  4. Click Continue.

Step 2: Download Google's metadata

Metadata is a small file, ending in .xml, that tells Tomba how to trust sign-ins from Google.

  1. On the Google Identity Provider details screen, download the metadata.

  2. Save the file on your computer. You'll upload it to Tomba in Step 4.

  3. Click Continue.

Step 3: Copy Tomba's details into Google

  1. In a new browser tab, open Settings > SAML SSO in Tomba.

  2. Find Service provider details.

  3. Copy each value into Google Admin, using the table below.

  4. Click Continue, then Finish.

Field in Google Admin

What to enter

ACS URL

ACS URL (Reply URL) from Tomba

Entity ID

Entity ID (Audience URI) from Tomba

Name ID format

EMAIL

Name ID

Basic Information > Primary email

Step 4: Upload the metadata to Tomba

  1. On the same Tomba page, click Configure SAML SSO.

  2. On the Upload file tab, choose the file you saved in Step 2.

  3. Check that you see Metadata looks good, with the Entity ID and SSO URL below it.

  4. Click Save and enable SSO.

Step 5: Turn on the app for your team

Google keeps a new app off until you turn it on.

  1. In Google Admin, open Apps > Web and mobile apps and select your Tomba app.

  2. Click User access.

  3. Select On for everyone, or choose only some groups of people. Google calls these groups organizational units.

  4. Click Save.

Google says changes can take up to 24 hours, but they usually apply sooner.

Step 6: Verify your email domain

Your team can only reach SSO sign-in once your email domain is verified. Follow Verify Your Domain for SSO before you test.

Step 7: Test the connection

  1. Open a private or incognito 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, then sign in with your Google account.

You should end up signed in to Tomba.

💡 Tip: Once this works, choose how your team signs in. See SSO Enforcement Modes.

Common questions

What should I check if I see "Authentication failed"?

Check these three things:

  • The app is turned on for your user in Google Admin.

  • The Entity ID and ACS URL in Google match Tomba exactly.

  • Name ID is set to Primary email.

Why do I see "SSO not configured"?

SSO isn't set up for that email domain yet. Check that the domain is verified under Verified domains on Settings > SAML SSO.

What if I see a certificate error?

Download the metadata from Google again. Then click Replace metadata on Settings > SAML SSO and upload the new file.

Related articles

Did this answer your question?