Social sign-on versus single sign-on
Key Takeaway
Single sign-on (SSO) lets users log in once and then move between many apps without logging in again. Social sign-on lets users log in to a Salesforce org with an account they already have, such as Google or Facebook.
Single sign-on (SSO) and social sign-on both cut down on usernames and passwords, so they are easy to confuse. The difference is the problem each one solves. SSO removes repeat logins as users move between apps and services. Social sign-on removes the need for a new account, because users log in to a Salesforce org, often an Experience Cloud site, with an account they already have.
Single sign-on versus social sign-on
Single sign-on (SSO) is an authentication method that gives users access to multiple applications with one login and one set of credentials. For example, after users log in to your org, they can open apps from the App Launcher without logging in again.
An external client app created without SSO acts like a bookmark. Users can open the app from the App Launcher, but they sometimes have to sign in again. Configuring the app for SSO removes that extra login. Configuring the app for SSO also lets admins set security policies and control who uses which apps.
Social sign-on lets users log in to a Salesforce org with the username and password they use for an external authentication provider, such as Facebook, X, LinkedIn, or Google. The org accepts those credentials, so the user doesn't create another account and password.
Social sign-on is especially useful for customers. They can log in to an Experience Cloud site with their Facebook or LinkedIn account instead of creating and remembering a new username and password.
To tell the two apart, ask what problem is being solved. SSO is about logging in once and then moving between many apps without logging in again. Social sign-on is about logging in with credentials from an existing social account.
Two people log in on the same Monday. Dana, a sales rep, logs in to her company's org. She then opens a travel booking app from the App Launcher without logging in again. She is using SSO, because one login gets her into many apps. Luis, a customer, visits the company's Experience Cloud site to check an order. He logs in with his Google account instead of creating a new password. He is using social sign-on, because he logs in with an account he already has.