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

Set up LinkedIn social sign-on

  • Updated

Create a LinkedIn developer app, enable Sign In with LinkedIn using OpenID Connect, add Bevy’s authorized redirect URLs, then send the Client ID and Client secret to Bevy over a secure channel so members can sign in with LinkedIn.

Bevy can show a Sign in with LinkedIn button on your community login and signup pages. Members authenticate with LinkedIn; Bevy then creates or signs in their community account.

Note: This page is for technical admins who create the LinkedIn developer app. For which social providers you can enable, see Introduction to social sign-on. Enterprise workplace SSO (Okta, Auth0, SAML, and similar) is separate — see Introduction to single sign-on. Members who use enterprise SSO follow Sign-in with single sign-on (SSO).

Tip: This setup is for LinkedIn login only. It is not the LinkedIn Insight Tag, partner ID, or conversion tracking. Chapter LinkedIn tracking is covered in Set LinkedIn tracking for a chapter. Community LinkedIn Insights Partner ID lives on Third-party services. Sibling providers: Set up Google social sign-on, Set up Facebook social sign-on, Set up X social sign-on.

Before you start

  • Access to LinkedIn Developers — My apps (you need permission to create or edit a LinkedIn developer app for your organization).
  • A LinkedIn Page associated with the app (LinkedIn requires a Company Page when you create the app).
  • Your Bevy community hostname (and staging or onboarding hostnames if Bevy asks you to whitelist them).
  • A secure way to share the Client ID and Client secret with Bevy (for example a password manager share or encrypted message — not email in plain text).

Create the LinkedIn developer app

  1. Open LinkedIn Developers — Create an app and create an app for this community. Use an app name members will recognize, associate a LinkedIn Page, and complete LinkedIn’s required fields (logo, privacy policy URL when prompted).
  2. Open the app’s Products tab and request Sign In with LinkedIn using OpenID Connect. LinkedIn usually grants this immediately.
  3. Confirm the Auth tab lists the OAuth 2.0 scopes openid, profile, and email after the product is enabled.

Tip: LinkedIn retired the older Sign In with LinkedIn product that used r_liteprofile and r_emailaddress. New apps must use Sign In with LinkedIn using OpenID Connect with the three scopes above.

Add authorized redirect URLs

On the app’s Auth tab, under Authorized redirect URLs for your app, add Bevy’s LinkedIn callback path for each hostname Bevy asks you to cover. Match the path exactly, including the trailing slash:

Environment Authorized redirect URL
Bevy test / staging sandbox https://<instance-id>-staging.bevylabs.com/accounts/linkedin_oidc/callback/
Onboarding instance https://<instance-id>.bevylabs.com/accounts/linkedin_oidc/callback/
Production community domain https://<your-community-domain>/accounts/linkedin_oidc/callback/

<instance-id> is the same ID used in your *.bevylabs.com subdomain. If you are unsure what it is, ask your Bevy contact or Bevy Support. <your-community-domain> is the final hostname members use when the community is live.

Important: Use /accounts/linkedin_oidc/callback/ — not /accounts/oidc/callback/ (that path is for enterprise OpenID Connect SSO) and not /accounts/linkedin_oauth2/…. A missing trailing slash or the wrong path will fail LinkedIn’s redirect check. Save (Update) on the Auth tab after you add each URL.

Tip: If Bevy only asks you to enable LinkedIn on production first, start with the production redirect URL. Add staging or onboarding rows when Bevy requests them.

What to share with Bevy

On the Auth tab, copy these values and send them over a secure channel to your Bevy onboarding contact or Bevy Support:

Item Required? What Bevy uses it for
Client ID Required Identifies your LinkedIn developer app.
Client secret (Primary Client Secret) Required Authenticates the Bevy application to LinkedIn. Share only over a secure channel.
Hostnames you whitelisted Recommended Confirm which environments (staging, onboarding, production) already have matching redirect URLs.

Important: Treat the Client secret like a password. Bevy configures LinkedIn on the community side — admins do not paste the secret into a public community settings screen.

After Bevy enables LinkedIn

  • A LinkedIn button appears on the community login and signup pages (placement relative to the email form follows your community’s login settings).
  • Members authenticate at LinkedIn, then return to Bevy on /accounts/linkedin_oidc/callback/.
  • Password resets for a LinkedIn sign-in path belong in the member’s LinkedIn account — not on Bevy’s Reset password page.

Note: Bevy requests LinkedIn’s openid, profile, and email scopes so it can create or match the community account. If login fails after enablement, confirm the Client ID, secret, product enablement, and redirect URL with Bevy Support before changing other LinkedIn app settings.