Meridian Global Health uses a custom object named Clinical_Trial__c to track medical research studies. The Organization-Wide Default (OWD) for Clinical_Trial__c is set to Private. The System Administrator is tasked with configuring access to satisfy two business requirements:
1. Managers must automatically gain access to Clinical_Trial__c records owned by their direct and indirect subordinates in the role hierarchy.
2. Members of the Compliance Team (a Public Group) must be granted Read/Write access to any Clinical_Trial__c record whenever its Status__c field is set to 'Under Review'.
Which TWO configuration steps must the administrator perform to satisfy these security requirements?
- Verify that the 'Grant Access Using Hierarchies' option is enabled on the Clinical_Trial__c custom object.Answer
- Create a criteria-based sharing rule on Clinical_Trial__c to grant Read/Write access to the Compliance Team public group when Status__c equals 'Under Review'.Answer
- CCreate an owner-based sharing rule to share records owned by subordinates with their respective role superiors.
- DAssign a Permission Set to the Compliance Team that overrides the Organization-Wide Defaults for Clinical_Trial__c to Public Read/Write.
Answer
The administrator must verify that 'Grant Access Using Hierarchies' is enabled for Clinical_Trial__c and create a criteria-based sharing rule that shares records where Status__c equals 'Under Review' with the Compliance Team public group with Read/Write access.
Enabling 'Grant Access Using Hierarchies' on a custom object ensures that users above record owners in the role hierarchy inherit access to those records. Additionally, criteria-based sharing rules provide a mechanism to share records with specific Public Groups based on record field values (such as Status__c = 'Under Review').
Step-by-Step Solution
Key Concept
Role Hierarchy Access Inheritance and Criteria-Based Sharing Rules
Estimated Time:1m 30s