An administrator at Global Renewables sets the Organization-Wide Default (OWD) for a custom object named Facility_Inspection__c to Private and deselects the 'Grant Access Using Hierarchies' option on the object definition to prevent automatic manager access. Executive leadership now requires that users assigned to the 'Safety Director' role receive Read-Only access to all Facility_Inspection__c records owned by users in the 'Inspector' role. Which configuration should the administrator implement to fulfill this requirement without re-enabling automatic role hierarchy access for all other roles?
- Create an owner-based sharing rule on Facility_Inspection__c that shares records owned by members of the 'Inspector' role with members of the 'Safety Director' role.Cevap
- BEnable the 'Grant Access Using Hierarchies' checkbox on the object definition and place the 'Safety Director' role directly above the 'Inspector' role in the role hierarchy.
- CCreate a criteria-based sharing rule that automatically re-enables hierarchy access specifically for users assigned to the 'Safety Director' role.
- DAssign a Permission Set containing the 'View All' object-level permission for Facility_Inspection__c to users in the 'Inspector' role.
Cevap
The administrator should create an owner-based sharing rule on Facility_Inspection__c that shares records owned by members of the 'Inspector' role with members of the 'Safety Director' role.
Creating an owner-based sharing rule allows the administrator to share records owned by users in the 'Inspector' role with users in the 'Safety Director' role with Read-Only access. This approach works when OWD is Private and operates independently of the 'Grant Access Using Hierarchies' setting on the custom object.
Adım Adım Çözüm
Anahtar Kavram
Owner-Based Sharing Rules vs. Custom Object Role Hierarchy Settings