Question

Difficulty: MediumOrganization-Wide Defaults (OWD)

Cloud Kicks uses a custom object named Patent_Filing__c to manage intellectual property documentation. Management requires that users can only view and edit Patent_Filing__c records that they own or that are owned by their subordinates in the role hierarchy. Additionally, members of the Executive Leadership public group must be granted View access to all Patent_Filing__c records across the organization.

Which two administration settings should the System Administrator configure to meet these record-level access requirements?

  1. Set the Organization-Wide Default (OWD) internal access for Patent_Filing__c to Private with Grant Access Using Hierarchies enabled.Answer
  2. Create a criteria-based or owner-based sharing rule that grants Read access on Patent_Filing__c records to the Executive Leadership public group.Answer
  3. C
    Modify the Standard User profile to grant View All object permissions on Patent_Filing__c to restrict visibility based on role.
  4. D
    Disable the Grant Access Using Hierarchies checkbox on the Patent_Filing__c custom object definition to enforce role hierarchy privacy.

Answer

The administrator must set the Organization-Wide Default internal access for Patent_Filing__c to Private with Grant Access Using Hierarchies enabled, and create a sharing rule that shares Patent_Filing__c records with the Executive Leadership public group.
To satisfy the requirement where only record owners and higher role hierarchy levels have access by default, the Organization-Wide Default (OWD) must be set to Private, and Grant Access Using Hierarchies must remain enabled. To grant additional access to executives who may sit outside the direct reporting hierarchy, a sharing rule must be implemented to extend Read permissions to their public group.

Step-by-Step Solution

1
Determine the most restrictive baseline sharing access needed for the custom object.
Since users should not see records owned by peers, the Organization-Wide Default must be set to Private.
OWD sets the baseline security level for records users do not own.
2
Ensure record access propagates vertically up the role hierarchy.
Keep 'Grant Access Using Hierarchies' enabled (checked) on the custom object.
This grants managers automatic access to records owned by their subordinates.
3
Extend access laterally to the executive team.
Configure a sharing rule to share records with the Executive Leadership public group.
Sharing rules are used to open up access beyond OWD baselines for specific user groups.

Key Concept

Organization-Wide Defaults (OWD) and Role Hierarchy Sharing Controls
Estimated Time:1m 30s
Rate this question