After giving partner admins permission to connect to the vendor’s Salesforce org, vendor
admins kick off the Partner Connect setup process by selecting a partner company to connect with.
After a vendor admin selects a partner, Salesforce sends an email to the partner admin with
instructions on how to complete the connection request.
Required Editions
Available in Lightning Experience in Enterprise and Unlimited
Editions with Sales or Service. Vendors must purchase a PRM add-on license for the partner admin
user and each partner user who exports records. Partners aren’t required to purchase
PRM licenses to use Legacy Partner Connect.
User Permissions Needed
To set up Partner Connect in a vendor org:
Customize Application
Make sure you authorized this partner to connect with your org by assigning the Partner Admin
Approved for Vendor Org Connection permission set.
From Setup, in the Quick Find box, enter PRM, and then select
Partner Connect for Vendors.
Under Connect, from the Invite Partners to Connect section, click Add
Partner.
Provide the partner account for the company you’re working with and the username of your
partner admin, and then click Save and Email Partner.
Partner Connect adds the partner account name to the external client app created for this
connection. That way, you and other admins at your company can see which external client app
connects you to each partner org. Partner Connect emails partner admin notifications to the
partner user that you provide.
This vendor is added to the Partner list. An email is sent to the partner admin with
details about your org and partner site that the partner admin must provide during their own
Partner Connect setup. When the partner admin completes the connection between orgs, the
connection status banner for this partner changes from Invitation Sent to Connected. But partner
users can’t export records from your Experience Cloud partner site until all vendor and partner
setup steps are complete.
The next setup step for vendor admins is to select the objects and fields that you want to
integrate with your partner’s org. You can proceed to that step before the partner admin
completes the connection between orgs.
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.
