An industrial manufacturing company uses a custom object named Equipment_Inspection__c to record machinery safety audits. Management mandates that plant technicians must only be able to view and edit inspection records that they personally own. However, plant managers require full read and edit access to all inspection records created by the technicians who report directly or indirectly to them. Which Organization-Wide Default (OWD) setting and configuration for Equipment_Inspection__c fulfills these requirements with the least administrative effort?
- Set Default Internal Access to Private and keep 'Grant Access Using Hierarchies' selected.Answer
- BSet Default Internal Access to Public Read/Only and use Profiles to restrict Read access for records not owned by the technician.
- CSet Default Internal Access to Private and deselect 'Grant Access Using Hierarchies', then create manual sharing rules for managers.
- DSet Default Internal Access to Public Read/Write and assign Permission Sets to block view access to unowned inspection records.
Answer
Set Default Internal Access to Private and keep 'Grant Access Using Hierarchies' selected.
Setting the Organization-Wide Default to Private ensures that plant technicians can only view and edit records they own. Leaving 'Grant Access Using Hierarchies' selected ensures that managers higher in the role hierarchy automatically inherit read and edit access to records owned by their subordinates.
Step-by-Step Solution
Key Concept
Organization-Wide Defaults (OWD) and Role Hierarchy Access
Estimated Time:1m 30s