Nova Biotech uses a custom object named Lab_Sample__c with an Organization-Wide Default (OWD) set to Private. Senior Scientists need Read access to all Lab_Sample__c records owned by Lab Technicians who report below them in the role hierarchy. Additionally, members of the Quality Assurance team (located in a separate role hierarchy branch) require Read/Write access to all Lab_Sample__c records where the Status__c field is set to 'Pending Inspection'. Which two configuration steps should the Salesforce Administrator take to satisfy these access requirements?
- Ensure 'Grant Access Using Hierarchies' remains enabled on the Lab_Sample__c custom object.Cevap
- BDeselect 'Grant Access Using Hierarchies' on Lab_Sample__c and create individual owner-based sharing rules for each Senior Scientist.
- Create a criteria-based sharing rule on Lab_Sample__c where Status__c equals 'Pending Inspection' to share records with a Public Group containing Quality Assurance members.Cevap
- DCreate a Permission Set granting 'View All' data permissions on Lab_Sample__c and assign it to the Quality Assurance team members.
- EChange the Organization-Wide Default (OWD) setting for Lab_Sample__c from Private to Public Read-Only.
Cevap
The administrator must ensure 'Grant Access Using Hierarchies' remains enabled on the custom object and create a criteria-based sharing rule granting Read/Write access to the Quality Assurance Public Group when Status__c equals 'Pending Inspection'.
Enabling 'Grant Access Using Hierarchies' ensures that higher roles in the hierarchy (Senior Scientists) automatically inherit access to records owned by subordinate roles (Lab Technicians). Furthermore, creating a criteria-based sharing rule grants the Quality Assurance Public Group Read/Write access specifically when the record field Status__c equals 'Pending Inspection', satisfying both security requirements cleanly.
Adım Adım Çözüm
Anahtar Kavram
Role Hierarchy Access and Criteria-Based Sharing Rules