Partner
A Partner in Salesforce is a company or individual you do business with through your sales channel, such as a reseller, distributor, value-added reseller, system integrator, or independent software vendor.
Definition
A Partner in Salesforce is a company or individual you do business with through your sales channel, such as a reseller, distributor, value-added reseller, system integrator, or independent software vendor. Partners sell, deliver, or support your products on your behalf instead of you selling directly to every end customer. In the data model a partner is represented by a partner account, which is a regular business account that has been enabled for partner access.
Partners are external to your company, so they are not employees and do not get full internal user licenses. Instead they log in to a partner portal built on Experience Cloud, where they can work the leads, deals, and resources you choose to share. Salesforce groups all of this under Partner Relationship Management (PRM), the set of features that onboard partners, route leads to them, and track how the channel performs.
How partner accounts, users, and PRM fit together
Partner account vs. customer account
A partner account starts life as an ordinary business account. It becomes a partner the moment an admin uses the Enable as Partner action on the account record, which flags it for external partner access and unlocks the related portal features. The difference is one of intent and access, not a separate object. A customer account represents someone who buys from you. A partner account represents a company that helps you sell or service those customers. Because the underlying object is the same Account, partner accounts share the same fields, page layouts, and reporting as customer accounts. You can still log activities, attach opportunities, and run reports against them. What changes is that the account can now host external users who log in to your partner site. One practical rule matters here: a partner account must be a business account, not a person account, and it should be owned by an internal user who has a role in the role hierarchy. That ownership requirement exists because partner data rolls up to the owner, which we cover next.
Partner users and the role hierarchy
People at a partner company log in as partner users. You create one by enabling a contact that sits under a partner account, using the Enable Partner User action on the contact record. When you enable the first external user on a partner account, Salesforce automatically builds a small three-level role hierarchy under the account owner: Partner User, Partner Manager, and Partner Executive. These roles sit below the internal account owner, so records owned by partner users roll up through the partner account to your team. That hierarchy controls visibility. A Partner Executive can see records owned by the Partner Managers and Partner Users beneath them, which lets a partner company manage its own people without seeing other partners' data. Partner users get a partner license, which is cheaper and more restricted than a full internal license. Their profile must be cloned from the standard Partner User profile, because standard internal profiles are not valid for partner users. Keep the API Only User permission off those cloned profiles, or the partner cannot log in to the portal at all.
What Partner Relationship Management actually does
Partner Relationship Management is the umbrella for the features that run a channel sales motion inside Salesforce. The classic problem it solves is the spreadsheet-and-email channel, where a vendor emails leads to partners and then loses all visibility into what happened. That approach does not scale, and it creates channel conflict when two partners chase the same deal. PRM replaces it with one shared system of record. The core capabilities map to the partner lifecycle. Onboarding gets new partners set up faster, since manual onboarding can take months. A lead inbox or lead routing assigns leads to the right partner without email, so you can track activity in real time. Deal registration lets a partner claim a deal they sourced, which protects their commission and reduces conflict. Channel marketing tools, including market development funds, help partners run demand generation on your behalf. Partner scorecards and dashboards then report on who is performing. All of this lives in the same org as your direct sales, so channel and direct pipeline sit side by side.
The partner portal on Experience Cloud
Modern partner portals are built on Experience Cloud, the platform Salesforce uses for external-facing sites. The Partner Central template is the starting point for a partner site. It ships with the layouts, navigation, and components partners expect, including lead and opportunity management, a campaign marketplace, and a place to find sales and marketing collateral. When a partner logs in to this site, they see a curated slice of your org. They can work the leads and opportunities shared with them, register deals, download approved content, and submit fund requests, all without ever touching your internal Salesforce UI. You decide exactly what is visible through profiles, permission sets, and sharing. The site is the partner-facing front door, while the partner account and partner users are the records behind it. This separation is why the same Account and Contact objects power both your internal teams and your external channel. You configure one set of data and expose a controlled view of it.
Sharing data with partners safely
Partners need some of your data but not all of it, and getting that boundary right is the heart of a good PRM setup. Sharing to partner users works the same way it works for any external user. The role hierarchy gives upward visibility, sharing rules and sharing sets grant access to specific records, and profiles plus permission sets control which objects and fields a partner can even open. A common pattern is to share leads and opportunities that a partner owns or is assigned, while hiding everything else. Because partner users sit at the bottom of the role hierarchy under the account owner, they do not see records owned by your internal reps unless you deliberately share them. This least-privilege default is intentional. It is far safer to start partners with narrow access and open up specific objects than to expose your whole org and try to lock it down afterward. Always test the partner experience by logging in as a partner user, since what an admin sees and what a partner sees can differ sharply.
When you would use partners instead of direct sales
Not every business needs PRM. You reach for partners when a meaningful share of your revenue flows through third parties rather than your own reps. Software vendors lean on resellers and independent software vendors to reach markets they cannot cover directly. Hardware and manufacturing companies sell through distributors and value-added resellers. Services firms work with system integrators who deliver the implementation. In each case the vendor wants the same things: give partners just enough access to sell effectively, avoid two partners fighting over one deal, and measure which partners actually produce. If your channel is small, a few partner accounts and some sharing rules may be all you need. As the channel grows, the full PRM stack pays for itself by removing the manual lead handoffs and giving you real reporting on channel pipeline. The decision is less about company size and more about how central the channel is to how you go to market.
Enable a business account as a partner account
Turning an existing business account into a partner account is a quick admin task, but it has prerequisites. Partner features must be enabled in your org, you need partner licenses available, and the account must be a business account owned by an internal user who has a role. Once those are in place, the steps below enable the account and its first partner user.
- Open the account record
Find the business account for the partner company. Confirm it is a business account, not a person account, and that its owner is an internal user with a role in the hierarchy. Partner data rolls up to that owner.
- Enable the account as a partner
From the account, choose the Enable as Partner action. This flags the account for partner access and makes it eligible to host external partner users. The account remains a normal account for all other purposes.
- Enable a contact as a partner user
Open a contact under that account and choose Enable Partner User. Assign a profile cloned from the standard Partner User profile and a partner license. Salesforce builds the Partner User, Partner Manager, and Partner Executive roles under the account owner on first enablement.
- Grant access and test the login
Use sharing rules, sharing sets, and permission sets to share the leads, opportunities, and resources the partner should see. Then log in as the partner user to confirm they see only what you intended in the Experience Cloud site.
Must be a business account. Person accounts cannot be enabled as partner accounts.
An internal user who holds a role in the role hierarchy, since partner user records roll up to this owner.
A profile cloned from the standard Partner User profile. Standard internal profiles are not valid for partner users.
Each partner user consumes a partner license, which must be available in your org before you enable them.
- Leave the API Only User permission unchecked on cloned partner profiles, or the partner cannot log in to the portal.
- Partner accounts cannot be deleted, only disabled. Plan account hygiene with that in mind.
- Disabling a partner user makes their partner role obsolete, so their records stop rolling up to the partner account.
- The Role field is read-only when you enable the first partner user on an account, but becomes editable for users you add afterward.
Prefer this walkthrough as its own page? How to Partner in Salesforce, step by step
Trust & references
Cross-checked against the following references.
Straight from the source - Salesforce's reference material on Partner.
- Create Partner AccountsSalesforce
- Create Partner UsersSalesforce
Hands-on resources to go deeper on Partner.
About the Author
Dipojjal Chakrabarti is a B2C Solution Architect with 29 Salesforce certifications and over 13 years in the Salesforce ecosystem. He runs salesforcedictionary.com to help admins, developers, architects, and cert/interview candidates sharpen their fundamentals. More about Dipojjal.
Test your knowledge
Q1. Through which Salesforce feature set is a Partner relationship typically managed?
Q2. What kind of business relationship does a Salesforce Partner usually represent?
Q3. How do Partners typically interact with the company's Salesforce data through PRM?
Discussion
Loading discussion…