This guide explains how to configure Single Sign-On (SSO) using GitLab (Cloud or Self-Managed) via the OAuth 2.0 protocol.
SSO is available on the Baserow Advanced and Enterprise plan. You must have a valid license activated to configure these settings.
The GitLab SSO integration allows users to log in to Baserow using their existing GitLab accounts.
This works for both GitLab.com and Self-Managed GitLab instances. To set this up, you must create an “Application” in your GitLab user settings (or Instance Admin settings) and connect it to Baserow.

Before registering the app in GitLab, you need to know where GitLab should send users after they log in.
https://baserow.yourdomain.com/api/sso/oauth2/callback).Baserowread_user. (This is the minimal scope required to identify the user).
GitLab will now display your Application ID and Secret.
GitLab.https://gitlab.com).https://gitlab.company.com).Learn more: Connect GitLab to Baserow
This often happens if the Callback URL in GitLab does not exactly match the URL Baserow is expecting.
http vs https)?If you are using a private GitLab instance, ensure your Baserow server can reach your GitLab server over the network. If they are on the same internal network, you may need to configure Docker networking or firewall rules to allow the connection.
Yes, but with caveats. Creating the app in a Group does not restrict login access to only members of that group; it just means that group owns the application. Any user on that GitLab instance (or GitLab.com) could potentially log in.
Learn more: Global instance settings
Not currently. Baserow supports Just-In-Time (JIT) provisioning, which creates the user account immediately upon login. However, it does not sync GitLab Group memberships to assign Baserow roles (e.g., Admin vs. Editor). You must manually assign roles in Baserow after the user logs in.
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.