Question

Difficulty: EasyOrganization-Wide Defaults (OWD)

Universal Containers wants to restrict baseline access to a custom object named Support_Ticket__c so that users can only view records they own. Additionally, managers must automatically retain access to records owned by their direct subordinates. Which TWO configurations must the administrator complete to meet these baseline access requirements?

  1. Set the Organization-Wide Default (OWD) sharing setting for Support_Ticket__c to Private.Answer
  2. B
    Create a permission set that restricts Read access for users who do not own the record.
  3. Ensure that the Grant Access Using Hierarchies checkbox remains selected for Support_Ticket__c.Answer
  4. D
    Deselect the Grant Access Using Hierarchies checkbox to allow managerial access while blocking peer visibility.

Answer

To configure the baseline security according to requirements, the administrator must set the Organization-Wide Default (OWD) for Support_Ticket__c to Private and ensure that Grant Access Using Hierarchies is checked.
Setting the Organization-Wide Default to Private ensures that record access is restricted by default to record owners. Keeping Grant Access Using Hierarchies checked allows users higher up in the role hierarchy to automatically inherit access to records owned by subordinate roles.

Step-by-Step Solution

1
Determine the most restrictive baseline access setting.
The Organization-Wide Default (OWD) setting for the custom object must be set to Private so non-owners cannot see each other's records by default.
OWD sets the default baseline access level for all records in the organization.
2
Verify role hierarchy access behavior for the custom object.
Ensure Grant Access Using Hierarchies is checked.
This setting allows higher-level roles in the hierarchy to inherit access to records owned by or shared with lower-level roles.

Key Concept

Organization-Wide Defaults (OWD) and Role Hierarchy Access
Rate this question