- 01Choose a provider
- 02Continue with your account
- 03Back on your site
Choose Google, GitHub or Facebook to sign in using an account you already have.
← All features
Social login & Google One Tap
Let members use an account they already know.
Offer Google, GitHub and Facebook sign-in, with Google One Tap for an additional way to enter your site.
Available in the current release.
See it in action
A familiar account. And you’re in.
Choose Google, GitHub or Facebook, continue with your signed-in account, and arrive back on your site.
Welcome back
Sign in to your WordPress site.
Username or emailalex@example.com
Password••••••••
or continue with
Sign in with GoogleContinue to your-site.com
Continue to your site
You’re already signed in to Google.
Alex Morganalex@example.com
Taking you back…
Your Google account is verified.
Googleyour-site.com
You're in
Welcome back, Alex.
You’re logged in with Google.
Your account✓ Signed in
Less typing. A familiar sign-in.
Why it matters
Another forgotten password can mean another lost visit.
Members may arrive ready to read a course, join a discussion or open their account, then get stuck at login. A familiar provider account gives them another way to return.
How it helps your site
Use a verified provider identity.
The provider handles its account authentication and FluentAuth receives the result through the configured OAuth flow. Your site does not need the user’s Google, GitHub or Facebook password. Required device verification still applies on your site.
What you gain
A shorter route back for returning members, with your site’s account and verification rules still in place.
Get FluentAuth →Inside FluentAuth
See the controls behind the experience.
Available in the current release.
Follow the setup guide →
How to connect a provider
- Create an OAuth application with the provider and register the callback URL shown in FluentAuth.
- Add the application’s credentials and enable that provider in your settings.
- Test a returning user and your intended registration flow from the front end.
Google One Tap adds a Google account prompt where you choose to display it. Its appearance also depends on the browser, the visitor’s Google session and provider behaviour.
Choose the option your audience recognises
GitHub can suit a developer community. Google may be familiar to a team or course audience. Keep the usual sign-in and recovery routes easy to find for people who cannot use a provider.
Does social login bypass my verification policy?
A required device factor still applies. Test your role policies with each enabled provider, along with account matching and registration settings, before inviting members to use the new flow.
For provider-specific instructions, see Google, GitHub, Facebook and Google One Tap.
Works well with
Build on this feature.
Give members a sign-in option they recognise.
Connect the providers your audience uses and test returning-user and registration journeys.