Create a Meta (Facebook) app, add Facebook Login, set Bevy’s Valid OAuth Redirect URIs, then send the App ID and App Secret to Bevy over a secure channel so members can sign in with Facebook.
Bevy can show a Sign in with Facebook button on your community login and signup pages. Members authenticate with Facebook; Bevy then creates or signs in their community account.
Note: This page is for technical admins who create the Meta (Facebook) Login 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 Facebook login only. It is not Meta Pixel, Facebook ads conversion tracking, or chapter/event pixel IDs. Pixel setup lives on Facebook pixel tracking and the community Facebook Pixel ID on Third-party services. Sibling providers: Set up Google social sign-on, Set up LinkedIn social sign-on, Set up X social sign-on.
Before you start
- Access to Meta for Developers — My Apps for an account that can create or edit a Meta app for your organization.
- A privacy policy URL Meta can accept when you take the app Live (often your community’s public privacy policy page).
- Your Bevy community hostname (and staging or onboarding hostnames if Bevy asks you to whitelist them).
- A secure way to share the App ID and App Secret with Bevy (for example a password manager share or encrypted message — not email in plain text).
Create the Meta app and add Facebook Login
- Open Meta for Developers — My Apps and create an app for this community. Choose a type Meta offers for consumer login (Meta’s create-app wizard labels change over time — pick the option that supports Facebook Login for a website).
- Add the Facebook Login product to the app if Meta did not add it during create.
- Open Facebook Login → Settings (or Facebook Login for Business → Settings, depending on your app type).
- Confirm these settings are on for a website redirect flow:
- Client OAuth Login
- Web OAuth Login
- Use Strict Mode for Redirect URIs
- Enforce HTTPS
Tip: Meta’s developer console labels move over time. If you do not see Facebook Login → Settings, open the app dashboard, find the Facebook Login product card, and open its settings. Bevy uses browser redirect OAuth — you do not need device or TV login options for this integration.
Add Valid OAuth Redirect URIs
Still under Facebook Login settings, add Bevy’s Facebook callback path to Valid OAuth Redirect URIs for each hostname Bevy asks you to cover. Match the path exactly, including the trailing slash:
| Environment | Valid OAuth Redirect URI |
|---|---|
| Bevy test / staging sandbox | https://<instance-id>-staging.bevylabs.com/accounts/facebook/login/callback/ |
| Onboarding instance | https://<instance-id>.bevylabs.com/accounts/facebook/login/callback/ |
| Production community domain | https://<your-community-domain>/accounts/facebook/login/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: A missing trailing slash, the wrong provider path (for example /accounts/oauth/…), or a URI that does not match the hostname members use will fail Meta’s redirect check. Save the Facebook Login settings after you add each URI.
Tip: If Bevy only asks you to enable Facebook on production first, start with the production redirect URI. Add staging or onboarding rows when Bevy requests them.
Finish App settings and go Live
- Open the app’s Settings → Basic (or equivalent App settings).
- Add your Privacy Policy URL (and any other required contact or category fields Meta shows before Live).
- Copy the App ID and App Secret (you may need to show or reset the secret).
- Switch the app from Development to Live (Meta may call this Live mode or publish the app) so members outside your developer roles can complete login.
Note: Meta can block Live mode until required fields (privacy policy, app icon, and similar) are complete. Fix those Meta requirements before you ask Bevy to enable the button for members.
What to share with Bevy
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 |
|---|---|---|
| App ID | Required | Identifies your Meta (Facebook) app. |
| App Secret | Required | Authenticates the Bevy application to Meta. Share only over a secure channel. |
| Hostnames you whitelisted | Recommended | Confirm which environments (staging, onboarding, production) already have matching Valid OAuth Redirect URIs. |
Important: Treat the App Secret like a password. Bevy configures Facebook Login on the community side — admins do not paste the secret into a public community settings screen.
After Bevy enables Facebook
- A Facebook button appears on the community login and signup pages (placement relative to the email form follows your community’s login settings).
- Members authenticate at Facebook, then return to Bevy on
/accounts/facebook/login/callback/. - Password resets for a Facebook sign-in path belong in the member’s Facebook account — not on Bevy’s Reset password page.
Note: Bevy requests Facebook’s email and public_profile scopes so it can create or match the community account. If login fails after enablement, confirm the App ID, App Secret, Live mode, and redirect URI with Bevy Support before changing other Meta app settings.