Skip to main content

SAML Single Sign-On

Let your team sign in to Tomba with the company login they already use.

Written by Tomba.io Team

Single sign-on (SSO) lets your team sign in to Tomba with the company login they already use, so they don't need a separate Tomba password. SAML is the standard that connects the two.

Your company's logins are managed by an identity provider. Tomba works with SAML 2.0 identity providers such as Okta, Microsoft Entra ID, Google Workspace and Salesforce.

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.

Why use SSO

  • One login. Your team uses the login they already know.

  • One place to control access. With Only SAML SSO, members must sign in through your identity provider. Owners and admins keep a password as a fallback.

  • No invitations needed. With Just-in-time provisioning, Tomba creates an account the first time someone signs in with SSO.

How setup works

  1. Add Tomba to your identity provider. You copy two values from Tomba into a new SAML app.

  2. Upload your metadata. Metadata is a small file from your identity provider. It tells Tomba to trust its sign-ins.

  3. Verify your email domain. You prove you own the domain your members sign in with.

  4. Test a sign-in. You check that it works before your team relies on it.

  5. Choose how members sign in. You make SSO preferred or required.

Settings > SAML SSO shows a checklist so you can see what's left. For the full steps, see Set Up SAML SSO.

Related articles

Did this answer your question?