Primary Partner
The Primary Partner is the single Partner Account on a Salesforce Opportunity flagged as the lead channel collaborator for that deal.
Definition
The Primary Partner is the single Partner Account on a Salesforce Opportunity flagged as the lead channel collaborator for that deal. Out of any number of partners linked to an opportunity through the Partners related list, exactly one carries the IsPrimary checkbox set to true. The primary flag drives commission attribution, partner-portal visibility, and standard reports that filter or group opportunities by their channel owner.
Primary Partner is a flag on the OpportunityPartner junction record, not a separate field on Opportunity. The platform enforces uniqueness: marking a second partner as primary automatically clears the flag on the previous primary, so the relationship stays one-to-one at any given time. This single-source-of-truth model is what makes channel reporting and partner compensation predictable; without it, an opportunity with three involved partners would have three competing claims to the deal.
Why the Primary Partner flag is the linchpin of channel reporting in Sales Cloud
The OpportunityPartner junction
Salesforce links Opportunities to Partner Accounts through the OpportunityPartner junction object, accessible via the Partners related list on the Opportunity record. Each row carries an OpportunityId, an AccountToId (the partner account), a Role (Distributor, Reseller, System Integrator, etc.), and an IsPrimary checkbox. The model supports many partners per opportunity, which is realistic in complex channel deals where one company sources the lead and another delivers the implementation.
Single primary at any time
The platform enforces that exactly one OpportunityPartner row per opportunity has IsPrimary set true. Setting the flag on a second partner automatically unsets it on the previous primary, in the same DML transaction. The platform-level enforcement matters because channel commission systems read the primary flag and assume it is canonical; without enforcement, two competing reads could attribute the same deal to two partners and create a double-pay incident.
Reporting and dashboards
The Primary Partner field is exposed on the Opportunity object as a read-only formula (Opportunity.Account_Primary_Partner__r or similar org-specific custom field). Channel reports group opportunities by primary partner to show pipeline contribution per partner, conversion rate per partner, and average deal size per partner. Without the primary flag, every report would need to handle the multi-partner case explicitly, which is verbose and error-prone. The flag also feeds the standard Opportunities with Partners report.
Partner portal visibility
When the partner program uses Experience Cloud (formerly Partner Communities), the primary partner determines which partner portal users can see the opportunity. A reseller's portal users see opportunities where their company is the primary partner, but typically not opportunities where another partner is primary even if they appear as a secondary collaborator. The sharing model is configurable, but the default treats primary as the access boundary because that is the safest commercial default.
Commission and revenue recognition
Most partner commission systems calculate payouts off the primary partner. A 20 percent referral commission on a $100k deal goes to the partner flagged primary, not split across the role table. This is intentional: complex multi-partner payouts can be modeled as separate Partner Commission records keyed to OpportunityPartner rows with secondary flags, but the primary flag remains the canonical channel attribution for the deal. Finance teams build their channel revenue ledger off this single field.
Channel attribution disputes
The most common partner-program incident is two partners both claiming primary on the same deal. Salesforce flags the conflict implicitly (only one row can have IsPrimary true at a time), so the question becomes which partner is correct. The standard resolution path is to read the Opportunity's CreatedBy, the source Lead record, any campaign attribution, and the Partner Activity Timeline to determine who actually sourced and influenced the deal. Channel ops then resets the flag and notes the resolution in a chatter post on the opportunity for audit.
Migrating from one primary partner to another
Changing the primary partner on a live opportunity has downstream effects. The previous primary loses portal visibility immediately, the new primary gains it, any in-flight commission calculations re-evaluate at the next batch, and reports re-categorize the deal under the new partner from the moment of the change. The change is logged in field history if the field is tracked. Channel ops typically only changes primary on an opportunity that has not yet closed; changing it post-close requires a finance recalculation and a written justification on file.
Set the Primary Partner on an Opportunity
Flag one of the linked partners as Primary so channel reports, partner-portal visibility, and commission systems treat them as the lead collaborator for the deal.
- Open the Opportunity
Navigate to the deal record. Scroll to the Partners related list. The list shows every Partner Account linked to the opportunity with their Role.
- Confirm the partners are linked
Every partner who will be reported on must appear here. If a partner is missing, click New Partner and link them with the appropriate Role before setting primary.
- Open the partner row to edit
Click the partner you want as primary. The OpportunityPartner detail opens with the IsPrimary checkbox visible.
- Check Primary
Mark IsPrimary true. Save. Salesforce automatically unsets the flag on any previously primary partner in the same transaction.
- Verify the change in reports
Open any channel-pipeline report. Confirm the opportunity now appears under the new primary partner. Refresh dashboards if needed.
- Document the change
For changes mid-deal or after close, add a Chatter post on the opportunity with the reason for the change. This is your audit evidence if commission is later disputed.
The flag on OpportunityPartner that designates the primary channel partner.
Picklist that classifies the partner (Distributor, Reseller, System Integrator, Referral). Independent of the primary flag.
Background junction between the customer Account and the Partner Account; the OpportunityPartner row is created when this relationship is invoked on a deal.
The team owning primary-partner accuracy. Without ownership, attribution drifts.
- The platform enforces exactly one primary at a time. There is no way to have zero primaries (if no partner is involved, leave the related list empty) and no way to have two.
- Changing primary on a closed opportunity has commission implications. Most channel programs require written justification for post-close changes.
- Partner portal visibility flips immediately when primary changes. A partner who was reading an opportunity yesterday may lose access today; communicate the change.
- The IsPrimary flag is not visible on standard list views by default. Add it to the related-list layout so reps can see at a glance which partner is currently primary.
Trust & references
Cross-checked against the following references.
- About PartnersSalesforce Help
- Assign a Primary PartnerSalesforce Help
- Partner Object ReferenceSalesforce Developer Docs
Straight from the source - Salesforce's reference material on Primary Partner.
- Partners DocumentationSalesforce Help
- OpportunityPartner Object ReferenceSalesforce Developer Docs
- Experience Cloud Partner SitesSalesforce Help
Hands-on resources to go deeper on Primary 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. What is a Primary Partner?
Q2. Why designate a primary partner?
Q3. When is this designation valuable?
Discussion
Loading discussion…