A pharmaceutical firm tracks sensitive clinical test findings using a custom object called Clinical_Trial_Response__c. Business governance mandates that clinical researchers must only be able to view and edit trial records they personally own. Additionally, managers positioned above the researchers in the role hierarchy must automatically inherit read and edit access to records owned by their subordinates, while researchers in other departments must have no access. Which Organization-Wide Default (OWD) setting and configuration satisfies these access requirements?
- Set the Organization-Wide Default to Private and keep 'Grant Access Using Hierarchies' enabled.Cevap
- BSet the Organization-Wide Default to Public Read-Only and use user profiles to restrict Read access for researchers in other departments.
- CSet the Organization-Wide Default to Private and deselect 'Grant Access Using Hierarchies', because custom objects automatically propagate access up the role hierarchy regardless of this setting.
- DSet the Organization-Wide Default to Public Read/Write and assign permission sets to revoke access from users outside the owner's department.
Cevap
Set the Organization-Wide Default to Private and keep 'Grant Access Using Hierarchies' enabled.
Setting the Organization-Wide Default to Private establishes the most restrictive baseline access so that users only see records they own. Keeping 'Grant Access Using Hierarchies' selected ensures users above the record owner in the role hierarchy automatically inherit access to those records.
Adım Adım Çözüm
Anahtar Kavram
Organization-Wide Defaults (OWD) and Role Hierarchy access propagation for custom objects