A commercial real estate company tracks confidential contract negotiations using a custom object named Lease_Agreement__c. Management requires that users only have access to records they own by default, while managers in the role hierarchy automatically inherit access to records owned by their subordinates. Which TWO configuration actions or principles should the administrator apply to establish this baseline access model?
- Set the Organization-Wide Default (OWD) for the Lease_Agreement__c object to Private.Answer
- Keep the 'Grant Access Using Hierarchies' checkbox selected for the Lease_Agreement__c object.Answer
- CModify user profiles to remove 'Read' permissions on Lease_Agreement__c to restrict baseline record-level visibility.
- DDeselect the 'Grant Access Using Hierarchies' option, as custom objects require sharing rules to grant access to managers.
Answer
The administrator must set the Organization-Wide Default (OWD) to Private for Lease_Agreement__c and keep the 'Grant Access Using Hierarchies' checkbox selected.
Setting the OWD for the custom object to Private ensures that users have no default access to records owned by others. Keeping 'Grant Access Using Hierarchies' enabled allows users above the record owner in the role hierarchy to automatically inherit access to those records.
Step-by-Step Solution
Key Concept
Organization-Wide Defaults (OWD) establish the baseline record-level access across the organization, while the 'Grant Access Using Hierarchies' setting allows access to automatically propagate up the role hierarchy.