Single sign-on (SSO) lets members open your Bevy community with credentials from an identity provider you configure. Learn what SSO changes for login, how many providers you can enable, and which IdPs Bevy supports.
Single sign-on (SSO) is a way for members to sign in to your Bevy community with an account they already use elsewhere — for example a company Okta, Auth0, SAML, OpenID Connect, or OAuth 2.0 identity provider (IdP). After the IdP authenticates them, Bevy signs them in. They do not need a separate Bevy-only password for that path.
SSO changes how people create accounts and sign in. It does not change how they use the community afterward. A member who signs in with SSO still RSVPs for events, joins chapters, and manages their profile the same way.
Note: This page is for technical admins who plan or enable SSO. Members who need sign-in steps should follow Sign-in with single sign-on (SSO).
What SSO changes for login
- Members authenticate at your identity provider instead of (or in addition to) a Bevy email and password.
- Your community can require SSO for every visitor, or show SSO alongside Bevy login and social buttons.
- Password resets for the SSO path belong at the identity provider — not on Bevy’s Reset password page.
- You can place SSO or social buttons above or below the login form under Settings → General. See Configure user account settings.
The SSO button on the login page follows your community’s styling.
How many providers you can configure
Bevy supports configuring one of each supported identity provider type. For example, you can enable one SAML IdP and one Okta configuration, but not two separate SAML apps for the same provider type.
You can also combine SSO with social sign-on so members see more than one sign-in option on the login page. Social providers (such as Google or LinkedIn) are separate from the enterprise IdP articles on this leaf. See Introduction to Social Sign On.
Tip: If you are choosing among OAuth 2.0, Auth0, Okta, OpenID Connect, and SAML, or deciding which profile fields the IdP must send, work with your Bevy contact or Bevy Support before you start provider setup.
Supported providers
Bevy supports these SSO providers. Each has its own configuration requirements — open the provider article for setup:
Why communities use SSO
- Fewer passwords for members — they sign in with credentials they already use at work or elsewhere.
- Stronger control for IT — authentication stays with your identity provider (including policies such as MFA).
- Less account administration in Bevy — you do not maintain a separate Bevy password for every SSO member.