Partner User
A Partner User is an external Salesforce user tied to a business partner account who logs in through an Experience Cloud site, usually with a Partner Community license.
Definition
A Partner User is an external Salesforce user tied to a business partner account who logs in through an Experience Cloud site, usually with a Partner Community license. Partner users are people at your resellers, distributors, agencies, or referral partners. They are not employees of your company, but they need controlled access to the leads, opportunities, and shared resources that let them sell or service on your behalf.
A partner user record is created by enabling a contact on a partner-enabled account. That link to a contact and account is what separates a partner user from an internal user. It is also what drives record sharing, role placement, and the data each partner sees. Partner users sit at the center of partner relationship management, where a vendor recruits a channel and gives each partner a slice of the CRM.
How partner users fit into a channel sales program
Contact plus account: the anatomy of a partner user
Every partner user starts as a contact on an account. The account must be enabled as a partner account, and its owner must hold a role in the internal role hierarchy. Without that owner role, Salesforce cannot place the partner under it, and the enable action fails. Once those conditions are met, an admin opens the contact and chooses Enable Partner User from the action menu. That spawns a user record bound to the contact, which is bound to the account. This three-way link does real work. The account groups partner users from the same company, so a reseller with ten salespeople shares one parent account. The contact gives each person a name, email, and title. The user record carries the login, profile, role, and license. Deactivating the user does not delete the contact, so history stays intact. If you ever disable the contact, every external user under it is disabled too. Understanding this chain helps you debug access problems, because a partner who cannot see a record is often missing the right account, role, or sharing path rather than a profile permission.
The Partner Community license and what it opens up
Most partner users run on a Partner Community license. It carries everything a Customer Community Plus license does, then adds the pieces a selling partner needs: sharing rules, roles, and reports and dashboards. That is why it is the standard choice for channel programs rather than the lighter customer licenses meant for support portals and self-service. A Partner Community user can work standard sales objects such as leads, opportunities, campaigns, and the records you choose to expose in the site. They can be granted permission to create and edit reports when the Reports and Dashboards tabs are added to the Experience Cloud site. They also participate in role-based sharing, which the customer-tier licenses do not offer. The license comes in two billing shapes. A member-based license is assigned to a named user who can log in as often as they like. A login-based license draws from a monthly pool, and each login consumes one credit, which suits partners who sign in occasionally. Both shapes let one user reach more than one Experience Cloud site, so a partner active in two programs needs only one seat.
Roles, sharing, and the partner account hierarchy
Partner users do not float free in your role hierarchy. When you enable the first partner user on an account, Salesforce builds a small role tree under the account owner, with up to three partner roles by default: Partner User, Partner Manager, and Partner Executive. Records owned by a user at one level roll up to the levels above, so a partner manager can see what the reps below them own. This mirrors how internal sales managers see their teams, but it stays scoped inside the partner account. Sharing rules then decide what data crosses from your internal users to partners and between partner accounts. Because every partner account creates its own roles, large channels can generate thousands of roles, which slows performance. Salesforce offers Account Role Optimization to cut that count, often down to a single role per account, while keeping the sharing behavior partners expect. Plan the role depth and sharing model early. Retrofitting sharing on a live partner site is far harder than designing it before the first reseller logs in.
Super user access and delegated administration
By default a partner user sees only the records they own, plus whatever sharing grants them. That is often too narrow for a partner team lead who needs visibility across colleagues. Super user access solves this. Enabled per user on Partner Community or Customer Community Plus licenses, it lets that person view and edit records owned by other partner users at their role and below, within the same partner account. A partner manager with super user access can pick up a deal a teammate started and keep it moving. Delegated external user administration pushes some admin work out to the partner. You can let a trusted partner contact create and manage other users inside their own account, reset their passwords, and assign profiles you approve. This takes routine provisioning off your internal team and lets partners run their own roster. Both features reduce the support load that comes with a growing channel. They also raise the stakes on profile and permission set design, because a delegated admin can only hand out the access you scoped, so scope it tightly.
Provisioning and the partner user lifecycle
Partner users follow a lifecycle that maps to the partner relationship itself. Onboarding creates the account, adds contacts for each person, and enables them as partner users with the right profile and role. A welcome email or a manual credential handoff gets them their first login. As the partnership runs, people change jobs, so you reassign roles, swap profiles, or move someone to super user access when they get promoted inside the partner. Offboarding matters just as much. When a person leaves the partner, deactivate their user promptly so they lose access while their records and history remain. When a whole partner relationship ends, you disable the contacts and freeze the users under that account. Treat this as routine program work rather than one-off admin tickets. Mature channel teams document who provisions partners, how access is reviewed, and how fast a departing partner is cut off. Periodic access audits catch stale accounts and over-broad sharing before they become a security gap. Self-registration and approval flows can automate parts of onboarding once your manual process is stable.
Common pitfalls when working with partner users
Several issues trip up teams new to partner users. The most frequent is the account owner without a role. If the owner of the partner account has no role in the hierarchy, you cannot enable any partner user on it, and the error message is not always obvious. Set the owner role first. Another is licensing confusion. Teams sometimes assign a Customer Community license to a partner, then find the user cannot use roles, sharing, or reports the way a reseller needs. Login type is a second trap. A member-based seat sits idle if a partner logs in twice a year, while a login-based pool can run dry if heavy users burn through credits. Match the model to real behavior. Sharing surprises are common too, since partners may see too much or too little depending on rules and super user settings. Always test as a partner user, not as an admin, because admin visibility hides sharing gaps. Finally, never use the broad Manage Users permission just to handle partner logins. Use Manage External Users instead, which scopes the access to what site administration actually requires.
How to create a partner user from a contact
You create a partner user by enabling an existing contact on a partner-enabled account. The internal-facing steps below assume you have the right admin permission and a Partner Community license available to assign.
- Enable the account as a partner
Open the account that represents the partner company. From the account actions, choose Enable As Partner so the account can host external partner users. Confirm the account owner holds a role in your role hierarchy, because Salesforce places partner users beneath that owner.
- Open the contact and enable the partner user
Go to the contact record for the person who needs access. From the contact action menu, select Enable Partner User. This opens a new user record already linked to that contact and its account.
- Assign the license, profile, and role
On the user record, set the User License to Partner Community, then pick a profile cloned from a partner template and a partner role such as Partner User. These three choices control login type, object permissions, and where the user sits in the partner hierarchy.
- Control the welcome notification and save
If your Experience Cloud site is not active yet, deselect Generate New Password And Notify User Immediately so the person is not emailed early. Save the record, then send credentials once the site goes live.
Set to Partner Community for a full selling partner. This opens up roles, sharing, and reports that customer-tier licenses do not provide.
A partner profile that grants the object and tab access the partner needs. Clone from a partner template rather than reusing an internal profile.
A partner role under the account owner, such as Partner User, Partner Manager, or Partner Executive. The role drives record roll-up within the partner account.
Inherited from the enabled contact. The contact must sit on a partner-enabled account whose owner has a role, or the enable action fails.
- The partner account owner must have a role in the hierarchy, or you cannot enable any partner user on that account.
- Disabling the parent contact disables every external user tied to it, so deactivate the user instead when only one person should lose access.
- Use the Manage External Users permission, not the broad Manage Users permission, to provision and reset partner logins.
- Test visibility while logged in as the partner user, since admin access masks sharing gaps that partners will actually hit.
Prefer this walkthrough as its own page? How to Partner User in Salesforce, step by step
Trust & references
Cross-checked against the following references.
- Create Experience Cloud Site UsersSalesforce
- Manage External UsersSalesforce
Straight from the source - Salesforce's reference material on Partner User.
- Experience Cloud User LicensesSalesforce
- Learn More About Experience Cloud LicensesSalesforce
Hands-on resources to go deeper on Partner User.
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. How does a Partner User access the company's Salesforce org?
Q2. Which records does a Partner User typically work with through the partner site?
Q3. How does sharing usually constrain what each Partner User can see?
Discussion
Loading discussion…