An administrator at Cloud Horizon Inc. is configuring record access for a custom object named Project_Audit__c. The Organization-Wide Default (OWD) for Project_Audit__c is set to Private. The administrator must grant read access to project audits under specific business requirements. Which two statements correctly describe how Salesforce record access mechanisms behave for this custom object? (Select 2 answers)
- Users in roles above the record owner in the role hierarchy automatically inherit read access to Project_Audit__c records when 'Grant Access Using Hierarchies' is enabled.Answer
- A criteria-based sharing rule can grant access to Project_Audit__c records to a Public Group based on field values, regardless of who owns the records.Answer
- CDeselecting 'Grant Access Using Hierarchies' on Project_Audit__c prevents sharing rules from extending access to users in higher roles.
- DAssigning a permission set with 'Read All' on Project_Audit__c changes the record ownership of private records to the assigned user.
- EAn owner-based sharing rule is required to grant access to users higher in the role hierarchy when the OWD is set to Private.
Answer
The correct statements are that users above the record owner in the role hierarchy automatically inherit access when 'Grant Access Using Hierarchies' is enabled, and that criteria-based sharing rules can share records with public groups based on field values regardless of record ownership.
In Salesforce data security, when Organization-Wide Defaults are set to Private, record access can be opened up using the role hierarchy and sharing rules. Enabling 'Grant Access Using Hierarchies' ensures superiors automatically inherit access to records owned by subordinates. Additionally, criteria-based sharing rules allow access to be granted to target groups based on record field values rather than owner assignments.
Step-by-Step Solution
Key Concept
Role Hierarchy and Sharing Rules Interaction with OWD