A healthcare company tracks sensitive employee safety compliance reports using a custom object named Safety_Incident__c. Business governance requires that baseline visibility to these records be restricted so that only the record owner and managers above them in the role hierarchy can view or edit the records. Users outside of the owner's direct role hierarchy line must have no access to these records. Which configuration of Organization-Wide Defaults (OWD) and hierarchy access settings correctly fulfills this requirement?
- Set the Organization-Wide Default for Safety_Incident__c to Private and ensure Grant Access Using Hierarchies is checked.Answer
- BSet the Organization-Wide Default for Safety_Incident__c to Private and uncheck Grant Access Using Hierarchies.
- CSet the Organization-Wide Default for Safety_Incident__c to Public Read-Only and assign a profile that removes Read access to records not owned by the user.
- DSet the Organization-Wide Default for Safety_Incident__c to Public Read/Write and apply a Permission Set Group to revoke visibility from non-owners.
Answer
Set the Organization-Wide Default for Safety_Incident__c to Private and ensure Grant Access Using Hierarchies is checked.
The correct option sets the Organization-Wide Default (OWD) to Private, which restricts default record access so non-owners cannot see the records. Keeping 'Grant Access Using Hierarchies' enabled ensures that managers higher in the role hierarchy inherit access to records owned by their subordinates.
Step-by-Step Solution
Key Concept
Organization-Wide Defaults (OWD) and Hierarchy Access