Single Sign-On (SSO) allows users to access Baserow using their existing corporate credentials, eliminating the need to manage separate usernames and passwords.
SSO is available on the Baserow Advanced and Enterprise plan. You must have a valid license activated to configure these settings.
Baserow SSO integrates with your identity provider (IdP) to centralize user access, improve security, and simplify employee onboarding.
Instead of signing up with a personal email, employees log in via your company’s central dashboard (like Okta, Azure AD, or Google Workspace). This ensures that when an employee leaves the company and is removed from your IdP, they automatically lose access to Baserow.
To configure SSO, you must be an Instance Admin. Navigate to the Admin Tools > General -> Authentication.

Before adding a provider in Baserow, you will generally need to set up an “Application” inside your Identity Provider’s dashboard.
You typically need to gather:
Baserow supports the three major industry standards for authentication.
Security Assertion Markup Language (SAML) is the standard for enterprise-grade identity management. It allows your Identity Provider (IdP) to pass authorization credentials to Baserow securely.
Supported dedicated integrations:
OAuth 2 is commonly used for “Social Login” or delegated access. It allows users to authorize Baserow to verify their identity via a third-party service without sharing their password.
Supported dedicated integrations:
OpenID Connect is an identity layer built on top of OAuth 2.0. It allows Baserow to verify user identity against any service that supports the OIDC standard, even if a dedicated integration is not listed above.
To view or add providers:
This error occurs if a user already has a Baserow account (created via Email/Password) and tries to log in via Okta SSO later. For security reasons, Baserow does not automatically merge these identities by default.
Solutions:
This option should only be considered if data loss is acceptable and after ensuring all data is backed up elsewhere.
BASEROW_ALLOW_MULTIPLE_SSO_PROVIDERS_FOR_SAME_ACCOUNT=true on the server. This allows merging but increases security risk.For optimal security, we recommend maintaining consistent authentication methods unless necessary. If enabling multiple login methods is essential, implement additional security measures to mitigate potential risks.
Learn more: SSO configuration
Yes. Administrators can disable the standard “Email and password” authentication method in the settings. This forces all users to log in via your configured SSO provider, ensuring strict adherence to company security policies.
Yes. You can configure multiple providers (e.g., “Google” for the marketing team and “GitHub” for the engineering team). Users will see buttons for all active providers on the login screen.
If the email address in Baserow matches the email address in the SSO provider, the user will be logged into their existing account. Baserow links the identity based on the email address.
Still need help? If you’re looking for something else, please feel free to make recommendations or ask us questions; we’re ready to assist you.