Configure Single Sign-On (SSO) with Salesforce as the Identity Provider
For Salesforce Voice with Partner Telephony, let reps use a single sign-on page to
log in to Voice and in to your partner telephony provider’s system. Configure Salesforce to
serve as your identity provider (IdP) and then follow your telephony provider’s instructions for
completing the setup. Before you start, ask your telephony provider for the instructions for
setting up SSO.
Before you begin, contact Salesforce Support to request the ability to create
connected apps. This requirement starts in Spring ’26.
Configure Salesforce as your identity provider.
From Setup, enter Identity Provider in the Quick Find box,
select Identity Provider, and enable it.
Click Download Metadata.
After setting up your external client app in the next step, use the downloaded
metadata XML file to help set up SSO in your external telephony system.
Create an external client app (ECA) to use for SSO.
Note We recommend using an external client app for SSO instead of a connected app. Starting in
Spring ’26, customers can’t create a connected app unless they request the ability to
create connected apps from Salesforce Support. To migrate a preexisting connected app,
see Create an External Client App from a Connected
App.
To allow access to the app, update the ECA App policies.
From Setup, enter External Client App Manager in the Quick
Find box. Select your ECA.
Click Edit.
On the Policies tab, under App Policies, select profiles for users who need access
to SSO login or select permission sets that you’re using for Salesforce Voice.
Save your changes.
To complete the SSO setup, follow your telephony provider’s guide.
Did this article solve your issue?
Let us know so we can improve!
Loading
Salesforce Help | Article
Cookie Consent Manager
Cookie Consent Manager
General Information
Required Cookies
Functional Cookies
Advertising Cookies
General Information
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.