Examkin

Question

Difficulty: HardOpportunity Teams and Team Selling Access

An organization uses Opportunity Teams to facilitate collaboration on complex deals. The Organization-Wide Default for Opportunities is set to Private. A sales representative adds a technical consultant to an Opportunity Team and assigns them 'Read/Write' Opportunity Access. However, when the consultant attempts to edit the opportunity, the system prevents them from saving changes and displays an insufficient privileges error. Which configuration issue is preventing the consultant from editing the Opportunity?

  1. The consultant's Profile or assigned Permission Sets grant only Read object-level permission for Opportunities.Answer
  2. B
    The Organization-Wide Default for Opportunities must be set to Public Read/Write before Opportunity Team Read/Write access can function.
  3. C
    The consultant must be assigned a new profile with the 'Modify All Data' administrative permission to receive team access.
  4. D
    The consultant must be positioned above the Opportunity owner in the Role Hierarchy to receive Read/Write team sharing permissions.

Answer

The consultant's Profile or assigned Permission Sets grant only Read object-level permission for Opportunities.
In Salesforce security architecture, Object-Level Security (CRUD) acts as a strict ceiling over Record-Level Sharing. Even if a user is granted 'Read/Write' access to an Opportunity via Opportunity Teams, Account Teams, or Sharing Rules, they cannot edit the record unless their Profile or assigned Permission Sets grant 'Edit' permission on the Opportunity object itself.

Step-by-Step Solution

1
Analyze the access layers in Salesforce security (Object-Level Security vs. Record-Level Sharing).
Identify that Object-Level Security (Create, Read, Edit, Delete permissions on Profiles/Permission Sets) sets the maximum permissions ceiling for a user.
Record-level sharing tools can expand access to specific records, but they can never grant capabilities beyond what object-level permissions allow.
2
Evaluate the Opportunity Team access configuration.
The user was granted 'Read/Write' record-level access on the specific Opportunity Team.
This record sharing permission is valid, but requires the user to possess at least 'Edit' object-level permission for Opportunities.
3
Identify the conflict causing the insufficient privileges error.
Since the consultant cannot edit the record despite having Read/Write team access, their object-level permissions must be limiting them to Read-only on the Opportunity object.
Without 'Edit' permission on the Opportunity object level, team Read/Write sharing cannot enable record editing.

Key Concept

Interaction between Object-Level Security (CRUD) and Record-Level Sharing (Opportunity Teams)
Rate this question

Topics

Opportunity Teams and Team Selling Access

More questions from this topic