Explanation: To restrict access to opportunities such that sales users can only access: Opportunities they own
Opportunities tied to accounts they own
The consultant should set the Opportunity access on the role hierarchy to "View All Opportunities associated with the accounts they own."
Key Points:
Organization-Wide Defaults (OWD): Setting OWD for Accounts and Opportunities to Private ensures that users cannot access records they don't own unless granted through sharing rules or role hierarchy.
Role Hierarchy Settings: Adjusting the role hierarchy allows users to access opportunities associated with accounts they own, even if they don't own the opportunity records themselves.
Opportunity Access on Roles:
Controlled Access: This configuration ensures that users see only the opportunities they own and those tied to their accounts, aligning with the requirement.
Salesforce Sales Cloud References:
Role Hierarchy and Sharing Settings: Set Your Organization-Wide Sharing
Defaults
Opportunity Access via Roles: Define Access to Opportunities
Grant Access Using Hierarchies: Roles and Internal Access
Why Options A and B are Incorrect:
Option A: While setting OWD to Private is necessary, it doesn't by itself grant access to opportunities tied to accounts the user owns.
Option B: Setting OWD to Public Read-Only would allow users to see all accounts and opportunities, which contradicts the requirement to restrict access.
By setting Opportunity access on the role to view all opportunities associated with the owner's accounts, Cloud Kicks ensures that sales users have appropriate access, fulfilling the specified access requirements.