Question

Difficulty: EasyOrganization-Wide Defaults (OWD)

A company wants to secure a custom object named Staff_Evaluation__c. The administrator must ensure that users can only access records they own, while managers above them in the role hierarchy are automatically granted access. Which TWO configuration steps should the administrator take to fulfill this requirement?

  1. Set the Organization-Wide Default (OWD) internal access for Staff_Evaluation__c to Private.Answer
  2. Ensure the Grant Access Using Hierarchies checkbox remains selected for Staff_Evaluation__c.Answer
  3. C
    Create a permission set that restricts record access for non-owner users.
  4. D
    Deselect the Grant Access Using Hierarchies setting on the custom object to restrict visibility strictly to owners.

Answer

To meet the requirements, the administrator must set the Organization-Wide Default (OWD) internal access for the custom object to Private and ensure that the Grant Access Using Hierarchies option is selected.
To restrict records so users only access what they own, the Organization-Wide Default must be set to Private. To allow managers automatic access to their subordinates' records, the Grant Access Using Hierarchies option must remain enabled.

Step-by-Step Solution

1
Determine the baseline Organization-Wide Default setting.
Setting internal access for Staff_Evaluation__c to Private restricts general access so users can only view and edit records they own.
OWD sets the most restrictive baseline level of access across the organization.
2
Verify role hierarchy access settings.
Ensuring Grant Access Using Hierarchies is checked allows superior roles in the hierarchy to access records owned by lower roles.
By default, custom objects inherit role hierarchy sharing, which opens access vertically for managers.

Key Concept

Organization-Wide Defaults establish the baseline record access, while the Role Hierarchy expands access vertically to managers when enabled.
Rate this question