Direct Users to an Experience Cloud Site after Authentication
When you set up single sign-on (SSO) with an authentication provider, use the
Experience Cloud site URL request parameter to send users to a specific site after
authenticating. With the site parameter, you can determine whether a user logs in to your
Salesforce org or in to an Experience Cloud site. This parameter can also change what type of
user the registration handler creates.
Required Editions
Available in: Lightning Experience and Salesforce Classic
Available in: Enterprise, Performance, Unlimited, and
Developer Editions
User Permissions
Needed
To view the settings:
View Setup and Configuration
To edit the settings:
Customize Application
AND
Manage Auth. Providers
For example, you set up a Google authentication provider to configure SSO with your
Salesforce org as the relying party. You want to send site users who log in with Google
credentials to a custom site, so you add the site parameter to your SSO
client configuration URL. A user goes to your org’s login page, clicks a Google login
button, and enters their Google credentials. After Google authenticates the user, Salesforce
redirects the user to your custom site.
If you add the site parameter to the Single Sign-On Initialization
URL, Salesforce sends site users to the site after they log in. If you add the parameter to
the Existing User Linking URL, the Continue to Salesforce link on the
confirmation page leads to the site.
Without the site parameter, Salesforce sends the user to
/home/home.jsp for a portal or standard application, or to the
default sites page for a site after authentication.
Example
When you create an authentication provider, initialization and callback URLs direct to the
appropriate My Domain login or site URL. In the example, URLsuffix is the
value you specified when you defined the authentication provider:
We use three kinds of cookies on our websites: required, functional, and advertising. You can choose whether functional and advertising cookies apply. Click on the different cookie categories to find out more about each category and to change the default settings.
Privacy Statement
Required Cookies
Always Active
Required cookies are necessary for basic website functionality. Some examples include: session cookies needed to transmit the website, authentication cookies, and security cookies.
Functional Cookies
Functional cookies enhance functions, performance, and services on the website. Some examples include: cookies used to analyze site traffic, cookies used for market research, and cookies used to display advertising that is not directed to a particular individual.
Advertising Cookies
Advertising cookies track activity across websites in order to understand a viewer’s interests, and direct them specific marketing. Some examples include: cookies used for remarketing, or interest-based advertising.