Solaris Energy Solutions tracks sensitive client site evaluations using a custom object named Site_Inspection__c. Management mandates that field technicians must only be able to view and edit Site_Inspection__c records that they explicitly own. Additionally, regional operations managers must automatically receive access to all Site_Inspection__c records created by their direct and indirect subordinates within the managerial role structure. Which configuration should the administrator implement to enforce these access controls using Salesforce security best practices?
- Set the Default Internal Access for Site_Inspection__c to Private and ensure Grant Access Using Hierarchies remains selected.Answer
- BSet the Default Internal Access for Site_Inspection__c to Public Read-Only and assign a permission set that revokes Read permissions for non-owners.
- CSet the Default Internal Access for Site_Inspection__c to Private, deselect Grant Access Using Hierarchies, and build a criteria-based sharing rule for operations managers.
- DSet the Default Internal Access for Site_Inspection__c to Public Read/Write and remove object-level Read access on user profiles for field technicians.
Answer
Set the Default Internal Access for Site_Inspection__c to Private and ensure Grant Access Using Hierarchies remains selected.
Setting the Organization-Wide Default (OWD) to Private enforces the baseline restriction that users can only access records they own. Keeping Grant Access Using Hierarchies enabled ensures that managers higher in the role hierarchy automatically inherit access to records owned by their subordinates without requiring redundant sharing rules.
Step-by-Step Solution
Key Concept
Organization-Wide Defaults (OWD) and Role Hierarchy access for custom objects