Opportunity Team Member
An Opportunity Team Member in Salesforce (OpportunityTeamMember in the API) is a standard junction object that adds a User to an Opportunity Team and grants that user configurable access to the parent Opportunity record.
Definition
An Opportunity Team Member in Salesforce (OpportunityTeamMember in the API) is a standard junction object that adds a User to an Opportunity Team and grants that user configurable access to the parent Opportunity record. Each Opportunity Team Member record holds an OpportunityId, a UserId, a TeamMemberRole picklist (Account Manager, Pre-Sales Consultant, Sales Manager, Sales Rep, etc.), and an OpportunityAccessLevel field set to Read or Edit. Opportunity Team Members are the deal-level equivalent of Account Team Members — they let multiple users collaborate on a specific deal with shared visibility and edit access, without affecting access to other deals on the same Account. This matters most in orgs where Opportunity organization-wide defaults are Private or Public Read Only, requiring an explicit grant for non-owner users to participate in deal work. Default Opportunity Teams (configured per User in Personal Settings) auto-populate Opportunity Team Members on every new Opportunity the user creates, so a sales rep's standard supporting cast (SE, SDR, manager) follows them across every deal automatically.
In plain English
“An Opportunity Team Member is one user added to the team working on a specific deal — like the sales rep, the solutions engineer, and the sales manager all collaborating on one Opportunity. Each gets a role and an access level (Read or Edit) for that one Opportunity, separate from the broader Account Team.”
Worked example
A sales rep is working a $400K Opportunity at MidsizeRetailer Co. The deal is technically complex and politically sensitive, so she pulls in three colleagues for this specific Opportunity: a solutions engineer to scope integration work, a deal-desk specialist to structure pricing, and a sales manager for executive cover. She opens the Opportunity, scrolls to the Sales Team related list, and adds three Opportunity Team Members: the SE with role "Solutions Engineer" and Edit access, the deal desk with role "Deal Desk" and Edit access, and the manager with role "Sales Manager" and Read access. All three can now see the Opportunity, contribute notes, and (for the two with Edit) update fields like close date, amount, and stage. Other Opportunities on the same Account remain untouched — the team grant is scoped to this one deal.
Why Opportunity Team Member matters
Opportunity Team Members and Account Team Members are distinct mechanisms. Adding a user to an Account Team grants them access to all Opportunities under that Account (governed by the Account Team Member's OpportunityAccessLevel field). Adding a user to an Opportunity Team grants access to that one Opportunity only. The two can be combined: Account Teams handle the steady-state team for an account, while Opportunity Teams add temporary specialists for individual deals.
OpportunityAccessLevel can only equal or exceed the org's Opportunity organization-wide default. If OWD is Public Read/Write, Opportunity Teams add no value — everyone already has edit access. Opportunity Teams matter when OWD is Private (only the owner has access) or Public Read Only (everyone reads, only the owner edits) — in those cases, granular team access is the primary collaboration mechanism. Setting access to Read on a Team Member when the OWD is Public Read/Write is silently ignored; the user retains the broader access granted by the OWD.
Default Opportunity Teams are configured per User and can be set to auto-add to every new Opportunity the user owns, with an option to add to existing Opportunities retroactively. This is convenient for stable selling pods where the same supporting cast follows every deal, but it can rapidly inflate Opportunity Team membership counts. Auditing default team configuration is a common periodic admin task in fast-growing sales orgs.
How organizations use Opportunity Team Member
Configures a Default Opportunity Team containing her solutions engineer, deal-desk specialist, and sales manager. Every new Opportunity she creates auto-populates with the three team members at the appropriate access level, ensuring consistent staffing across her pipeline without manual setup.
Adds partner-side reps as Opportunity Team Members on co-sold deals with role Partner Co-Seller and Read access. Partner reps can monitor deal progression but cannot accidentally edit deal fields, while internal team members retain Edit access for actual deal work.
Avoids Opportunity Teams entirely and relies on Public Read/Write OWD for Opportunities — everyone can see and edit any deal. Opportunity Team Member rows are unused because they would add no incremental access. Common pattern for transactional sales motions where deal-level collaboration is unrestricted by design.
Trust & references
Straight from the source — Salesforce's reference material on Opportunity Team Member.
- Opportunity Teams in Salesforce HelpSalesforce
Discussion
Loading discussion…