A corporate training firm uses a custom object named Certification_Attempt__c to track employee exam results. Executive leadership mandates that test results must remain confidential: individual employees should only see their own exam records, while managers higher in the role hierarchy must be able to view and edit records owned by their direct reports. No other users should have access to records they do not own. Which Organization-Wide Default (OWD) configuration meets these security requirements?
- Set the Default Internal Access for Certification_Attempt__c to Private and keep Grant Access Using Hierarchies selected.Answer
- BSet the Default Internal Access for Certification_Attempt__c to Public Read/Write and remove Object Read permissions on profiles of non-manager users.
- CSet the Default Internal Access for Certification_Attempt__c to Private and deselect Grant Access Using Hierarchies, creating criteria-based sharing rules for managers.
- DSet the Default Internal Access for Certification_Attempt__c to Public Read-Only and assign permission sets to restrict visibility for peers.
Answer
Set the Default Internal Access for Certification_Attempt__c to Private and keep Grant Access Using Hierarchies selected.
Setting the Organization-Wide Default (OWD) to Private restricts baseline record access so users can only view and edit records they own. Leaving 'Grant Access Using Hierarchies' enabled ensures that users higher in the role hierarchy automatically inherit the owner's access level, fulfilling the requirement for manager access without exposing data to peers.
Step-by-Step Solution
Key Concept
Organization-Wide Defaults (OWD) establish the baseline record-level access. Setting an OWD to Private ensures users only access records they own, while Grant Access Using Hierarchies automatically propagates access up the role hierarchy.