A company uses a custom object named Project_Proposal__c with an Organization-Wide Default (OWD) set to Private. The administrator needs to ensure that managers automatically gain record access to proposals created by their direct subordinates in the role hierarchy, and that all members of the Finance team have read-only access to all proposals. Which two administration settings will fulfill these requirements? (Select 2)
- Ensure 'Grant Access Using Hierarchies' remains enabled for the Project Proposal custom object.Answer
- Create a sharing rule to share all Project Proposal records with the Finance role or public group with Read-Only access.Answer
- CCreate a permission set with Read access on the Project Proposal object and assign it to the Finance team members.
- DDeselect 'Grant Access Using Hierarchies' on the Project Proposal object to allow manager access through role assignment.
Answer
The correct configurations are ensuring 'Grant Access Using Hierarchies' remains enabled for automatic manager access via the role hierarchy, and creating a sharing rule granting Read-Only access to the Finance role or public group.
For custom objects with Private OWD, enabling 'Grant Access Using Hierarchies' ensures managers inherit record visibility from subordinate record owners. Additionally, a sharing rule is the standard mechanism to grant access to a broader group of users like the Finance team beyond OWD.
Step-by-Step Solution
Key Concept
Role Hierarchy and Sharing Rules record access expansion
Estimated Time:1m 0s