---
schema_version: "1"
id: f7c70fe660e8bd8867a9d620431494b3662b7da317b2a8b6ee81c576bb967d2e
title: Set Up Legacy Partner Connect as a Partner
collection: admin
version: current
locale: en-us
portal_url: https://docs.salesforce.com/admin/current/en-us/slack/264-0-0/prm_pc_setup_partner_parent.md
canonical_url: https://help.salesforce.com/s/articleView?id=slack.prm_pc_setup_partner_parent.htm&release=264.0.0&type=5
source_site: help.salesforce.com
content_type: documentation
content_hash: 6bd3a3dc68f1c40a12c3b5e09381f76bd9d8b117d7346de19ec2e99cc9194e25
description: 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.
products:
  - Sales
  - Slack
  - Cross Cloud
release: "264"
---
# 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.

<table class="slds-table slds-table_bordered slds-max-medium-table_stacked slds-m-bottom_small "><colgroup><col></colgroup><tbody><tr class=""><td class="slds-cell-wrap" style="vertical-align:top;">Available in Lightning Experience in <strong>Enterprise</strong> and <strong>Unlimited</strong> Editions with Sales or Service. Vendors must purchase a <a href="https://help.salesforce.com/s/articleView?id=slack.prm_support_license_template.htm&amp;type=5&amp;language=en_US" target="_blank">PRM add-on license</a> 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.</td></tr></tbody></table>

1. **[Give Partner Admins Access to Partner Connect Setup](https://help.salesforce.com/s/articleView?id=slack.prm_pc_setup_partner_assign_partner_admin_perm_set.htm&release=264.0.0&type=5)**  
    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.
2. **[Turn On Legacy Partner Connect as a Partner](https://help.salesforce.com/s/articleView?id=slack.prm_pc_setup_partner_enable.htm&release=264.0.0&type=5)**  
    To get started with Partner Connect, partner admins must first turn on the feature from Setup.
3. **[Configure Partner Org Settings for Legacy Partner Connect](https://help.salesforce.com/s/articleView?id=slack.prm_pc_setup_partner_configure.htm&release=264.0.0&type=5)**  
    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.
4. **[Connect to a Vendor Org with Legacy Partner Connect](https://help.salesforce.com/s/articleView?id=slack.prm_pc_setup_partner_add_vendor.htm&release=264.0.0&type=5)**  
    After receiving an email from Salesforce, you have the details that are required to establish a connection with your vendor.
5. **[Map Your Preferred Objects and Fields to Your Vendor’s Org](https://help.salesforce.com/s/articleView?id=slack.prm_pc_prm_pc_setup_partner_map.htm&release=264.0.0&type=5)**  
    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.