Planned maintenance: Tue Dec 8, 11:30pm–12:30am ET (8:30–9:30pm PT / Wed 5:30–6:30am CET). Brief downtime possible (up to 15 minutes).

Status page
Skip to main content

How can we help?

Need help? Check out our documentation or contact support

Search

Introduction to social sign on

  • Updated

Social sign-on lets members open your Bevy community with a Google, LinkedIn, Facebook, or X account. Learn which providers you can enable, how they work with enterprise single sign-on, and where each provider’s setup article lives.

Social sign-on lets members create an account or sign in to your Bevy community with a social account they already use — Google, LinkedIn, Facebook, or X. After the provider authenticates them, Bevy signs them in. They do not need a separate Bevy-only password for that path.

Social sign-on changes how people create accounts and sign in. It does not change how they use the community afterward. A member who signs in with Google still RSVPs for events, joins chapters, and manages their profile the same way.

Note: This page is for technical admins who plan or enable social providers. Members choose the social button on the login page. Enterprise SSO member steps are in Sign-in with single sign-on (SSO).

Social sign-on vs enterprise single sign-on

Bevy supports two related login options:

  • Social sign-on — consumer providers such as Google, LinkedIn, Facebook, and X. Setup for each provider lives on this leaf.
  • Enterprise single sign-on (SSO) — workplace identity providers such as Okta, Auth0, SAML, OpenID Connect, or OAuth 2.0. See Introduction to single sign-on.

You can enable social providers on their own, or combine them with enterprise SSO so the login page shows more than one option.

Tip: Social sign-on is for login buttons only. It is not Meta Pixel, LinkedIn Insight Tag, or other marketing / advertising pixels.

What social sign-on changes for login

  • Members authenticate at the social provider instead of (or in addition to) a Bevy email and password.
  • Enabled providers appear as buttons on the login and signup pages.
  • You can place social (and SSO) buttons above or below the login form under Settings → General. See Configure user account settings.
  • Password resets for a social path belong at that provider — not on Bevy’s Reset password page.

How many providers you can enable

You can turn on one social provider, several, or all of them — individually or at the same time. Each provider needs its own developer app and credentials.

After you create the app in the provider’s developer console, send the client ID (or app ID) and secret to Bevy over a secure channel. Bevy finishes the connection for your community. Provider articles list the exact redirect URI and fields Bevy needs.

Note: If you are unsure which providers to offer, or how social sign-on should work with enterprise SSO, work with your Bevy contact or Bevy Support before you start console setup.

Supported providers

Bevy supports these social sign-on providers. Each has its own setup article:

X appears as Twitter in some older developer-console labels and Help Center URLs. Use the X (Twitter) setup article for that provider.