Single Sign-On (SSO)
Last updated: July 28, 2026
Log in methods determine how your team accesses Bridgit. Basic Authentication (username and password) is available to all customers by default. Single Sign-On (SSO) allows your team to access Bridgit using your organization's existing identity provider credentials, simplifying login for your users.
Bridgit supports the following SSO authentication methods:
Microsoft OAuth 2.0
Google OAuth 2.0
SAML (instructions can be found here)
Eligibility
SSO authentication is available to all customers upon request. Contact Bridgit Support to begin setup.
How to Set Up SSO
Microsoft OAuth 2.0 or Google OAuth 2.0 Setup
Setting up SSO as a First Step
Customers have the option of restricting all users to SSO login from initial setup. Contact your Implementation Manager to have your account configured this way.
Active Users in Account
If active users have already been invited into the account, we also offer SSO setup as a Phase 2.
Note: Configuring SSO after users have already accepted their account invitations will reset all users, requiring them to accept a new invitation.
Common Questions
Q: How long does SSO setup take?
Setup typically takes 1-2 business days after a request has been made.
Q: Can I test SSO before rolling it out to my entire team?
Yes, you can assign SSO access to specific users or groups in your identity provider to test before full deployment.
Q: Can I use SSO for multiple Bridgit accounts?
Yes, SSO is configured at the organization level. SSO will apply to all accounts within your organization.
Q: Do I need to be on a specific plan to use SSO?
No. SSO authentication is available to all customers upon request. Contact Bridgit Support to begin setup.
Q: Can I still set up SSO if some users created a user name and password during the initial account creation?
Yes. However, SSO setup as a phase 2 means that all users will be reset in the account, and will need to accept a new invitation.