Question

Difficulty: EasyOrganization-Wide Defaults (OWD)

An administrator needs to configure record access for a custom object named Project_Milestone__c. The business requirement specifies that users should only be able to view and edit milestone records they own, while managers above them in the role hierarchy should automatically retain access to those records. Which TWO settings must the administrator configure?

  1. Set the Organization-Wide Default (OWD) for Project_Milestone__c to Private.Answer
  2. Ensure the Grant Access Using Hierarchies checkbox is selected for Project_Milestone__c.Answer
  3. C
    Create a permission set to restrict read and edit access for users who do not own the record.
  4. D
    Deselect the Grant Access Using Hierarchies checkbox on user profiles.

Answer

The administrator must set the Organization-Wide Default for Project_Milestone__c to Private and ensure that Grant Access Using Hierarchies is selected.
Setting the Organization-Wide Default to Private establishes the most restrictive baseline access where users only view records they own. Keeping Grant Access Using Hierarchies enabled ensures managers automatically inherit access to records owned by their subordinates.

Step-by-Step Solution

1
Determine the baseline access level required for non-owners.
The requirement specifies that users should only see their owned records, which demands a Private OWD setting.
OWD establishes the most restrictive baseline access level for records across the organization.
2
Ensure role hierarchy access propagation.
Verify that 'Grant Access Using Hierarchies' is enabled for the custom object.
By default, Grant Access Using Hierarchies is enabled for custom objects and allows managers to access records owned by direct reports.

Key Concept

Organization-Wide Defaults baseline security and role hierarchy access propagation
Estimated Time:1m 0s
Rate this question