Examkin

Question

Difficulty: HardRole Hierarchy and Sharing Rules

A healthcare organization tracks sensitive patient interactions using a custom object named Patient_Feedback__c. The Organization-Wide Default (OWD) sharing setting for Patient_Feedback__c is set to Private, and the administrator has deselected the 'Grant Access Using Hierarchies' checkbox to prevent automatic upward access propagation. The compliance team now requires that users assigned to the 'Quality Assurance Director' role receive Read access to all Patient_Feedback__c records owned by users in the 'Intake Specialist' role, while ensuring that users in the intermediate 'Intake Manager' role (who sit directly above Intake Specialists in the role hierarchy) do not gain access to these records. Which statement correctly describes the outcome when the administrator configures an owner-based sharing rule from the Intake Specialist role to the Quality Assurance Director role?

  1. The sharing rule grants Read access exclusively to users in the Quality Assurance Director role, and Intake Managers remain unable to view the records.Answer
  2. B
    The sharing rule cannot be created because owner-based sharing rules require the 'Grant Access Using Hierarchies' option to be enabled on custom objects.
  3. C
    The sharing rule grants Read access to Quality Assurance Directors, but access automatically propagates to Intake Managers because role hierarchy overrides sharing rules.
  4. D
    The administrator must create a new profile for Intake Managers with object-level restrictions to prevent them from inheriting the shared records.

Answer

The sharing rule grants Read access exclusively to users in the Quality Assurance Director role, while users in the Intake Manager role remain unable to view the records.
For custom objects, administrators can deselect 'Grant Access Using Hierarchies' to prevent managers from automatically inheriting access to records owned by subordinates. Creating an owner-based sharing rule targeted specifically to the Quality Assurance Director role grants access exclusively to users within that role, leaving intermediate manager roles without access.

Step-by-Step Solution

1
Analyze Organization-Wide Defaults and Hierarchy Settings
Patient_Feedback__c is Private with 'Grant Access Using Hierarchies' deselected. This means only record owners (Intake Specialists) and users granted explicit access can view records; higher roles like Intake Managers do not inherit access automatically.
For custom objects, disabling hierarchy access prevents managers from gaining implicit access to records owned by subordinates.
2
Evaluate the Owner-Based Sharing Rule Target
Configuring an owner-based sharing rule sharing records owned by 'Role: Intake Specialist' with 'Role: Quality Assurance Director' opens access specifically to members of the Quality Assurance Director role.
Sharing rules expand record access beyond OWD to specific roles, public groups, or territories.
3
Determine Access Propagation behavior
Because 'Grant Access Using Hierarchies' is disabled, access granted to Quality Assurance Directors does not propagate to intermediate roles like Intake Manager.
Disabling hierarchy access ensures sharing rules only grant access to the explicitly targeted role or group.

Key Concept

Interaction between Grant Access Using Hierarchies and Sharing Rules on Custom Objects
Estimated Time:2m 0s
Rate this question

Topics

Role Hierarchy and Sharing Rules

More questions from this topic