You are here:
Set Up Legacy Partner Connect as a Partner
After vendor admins kick off Partner Connect setup, partner admins get an email that describes how to start setup in a partner Salesforce org. Partner admins must be granted permission to access Partner Connect setup. Then partner admins turn on Partner Connect, configure some partner org settings, connect with the vendor org, and map their objects and fields to the objects and fields shared by the vendor.
| 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. |
- Give Partner Admins Access to Partner Connect Setup
Before partner admins can begin Partner Connect setup, they must be assigned the permissions required to access the setup page. Partner admins require the Customize Application permission and the Partner Connect Partner Admin Setup permission set. - Turn On Legacy Partner Connect as a Partner
To get started with Partner Connect, partner admins must first turn on the feature from Setup. - Configure Partner Org Settings for Legacy Partner Connect
Before completing the vendor’s connection request, partner admins must manage their required fields. If partners want to store read-only versions of their vendor’s records locally, partner admins must also prepare Partner Connect objects for storing the vendor records. To make sure users can see the vendor records from the partner org, partner admins must add related lists for Partner Connect objects to their Lead and Opportunity page layouts. - Connect to a Vendor Org with Legacy Partner Connect
After receiving an email from Salesforce, you have the details that are required to establish a connection with your vendor. - Map Your Preferred Objects and Fields to Your Vendor’s Org
After your vendor selects their object and field mappings, you get an email for each object. The emails instruct you on how to complete your mappings. First we guide you through importing your vendor’s object and field selections. Then you select a default user to assign to imported records. Lastly, you select the fields that you want to map to your vendor’s fields. If your vendor elected to send and receive field updates across orgs, you must also review storage options.
¿Resolvió este artículo su problema?
¡Háganos saber cómo podemos mejorar!
