This is useful for a superhost when you want to reduce sign-in friction and make the community easier to access. Members can use supported social accounts such as Google, Facebook, or LinkedIn for a quicker login experience.
Only community hosts can enable Social Login in the community.
This is important because Social Login affects how members access the community and therefore should be managed only by users with administrative access.
Before enabling any provider, keep this overall flow in mind:
Open Community Settings > Single Sign-On > Social Login.
Click Configure next to the provider you want to enable.
Create the corresponding app in that provider’s developer portal.
Copy the app credentials from that portal.
Paste those credentials into the provider popup in Zoho CommunitySpaces.
Copy the Redirect URL shown in CommunitySpaces.
Return to the provider’s developer portal and add that redirect URL in the appropriate callback or redirect setting.
Save the changes.
This sequence is important because the provider app and the CommunitySpaces configuration depend on each other. In most cases, you first create the provider app and collect its credentials, then use the Redirect URL shown in CommunitySpaces to finish the connection.
Use LinkedIn when you want members to sign in with their LinkedIn account.
In Social Login, click the developer portal link shown for LinkedIn.
In the LinkedIn developer page, enter the required app configuration details and create the app.
After the app is created, open the Auth tab.
Copy the Client ID and Client Secret.
Return to Community Settings > Single Sign-On > Social Login.
Click Configure next to LinkedIn.
In the popup:
Paste the Client ID into Application ID
Paste the Client Secret into Application Secret
Click Save.
After saving, copy the Redirect URL shown in the Social Login settings.
Go back to the LinkedIn Auth tab.
Under OAuth 2.0 settings, click + Add redirect URL.
Paste the copied Redirect URL.
Click Update.
That completes the LinkedIn setup for the community.
Use Facebook when you want members to sign in with their Facebook account.
In Social Login, click the developer portal link shown for Facebook and sign in to your Facebook for Developers account.
If you are new to the platform, first create a developer account.
Click My Apps in the top-right corner.
Click Create App.
Choose Allow people to login with their Facebook Account.
Click Next.
Choose whether you want to connect the app with a business portfolio.
Click Next.
Enter the App Display Name and App Contact Email.
Click Create App.
Complete the security check if prompted.
After the app is created, you will be taken to the app dashboard.
Search for and select Facebook Login.
Click Set Up.
After setup, open QuickStart.
Enter your Site URL.
Click Save, then Continue.
Click Next through the remaining steps, since they do not require additional configuration.
Open App settings > Basics from the left menu.
Copy the App ID and App secret.
Return to Community Settings > Single Sign-On > Social Login.
Click Configure next to Facebook.
In the popup:
paste the App ID into Application ID
paste the App secret into Application Secret
Copy the Redirect URL shown on the same page.
Go back to your Facebook developer app.
Open Advanced under App settings.
Paste the copied Redirect URL into the Share Redirect Allow List.
Click Save Changes.
That completes the Facebook setup for the community.
Use Google when you want members to sign in with their Google account.
In Social Login, click the developer portal link shown for Google and sign in to your Google developer console.
If you are new, first create a developer account.
Click Create project in the top-left.
Enter the Project name.
Select the required location.
Click Create.
From the notification, click Select Project.
On the project page, click the search bar.
Search for APIs & Services.
Open Credentials from the left menu.
Configure the consent screen if needed
If the consent screen is not already configured:
Click Configure consent screen. If the consent screen is already configured, continue directly to creating credentials.
Enter the App name and User support email.
Click Next.
Select the required audience preference.
Provide the contact details in the next steps.
Click Create to complete the consent screen setup.
Click + Create Credentials below the search bar.
Select OAuth client ID.
Choose Web Application as the Application type.
Enter a name for the OAuth client ID.
Return to Community Settings > Single Sign-On > Social Login.
Copy the Redirect URL shown in the page.
Go back to Google Cloud.
Under Authorized redirect URIs, click Add URI.
Paste the copied Redirect URL.
Click Create.
After the OAuth client is created, copy the Client ID and Client Secret from the popup.
Return to Community Settings > Single Sign-On > Social Login.
Click Configure next to Google.
Paste:
the Client ID into Application ID
the Client Secret into Application Secret
Click Save.
That completes the Google setup for the community.
Once Social Login is enabled, members can sign in to the community using the configured social provider.
Even after Social Login is enabled, users can still continue using the regular sign-up and login method as well.
This gives a superhost the benefit of faster sign-in options without removing the traditional access path for members who still prefer it.
Next: After enabling Social Login, continue with Paid Membership to configure paid access to the spaces in the community.