Examkin

Soru

Zorluk: OrtaOrganization-Wide Defaults (OWD)

A global logistics provider uses a custom object named Vendor_Dispute__c to track contract disputes with carrier partners. Security policy mandates that standard employees should only have access to vendor dispute records they own. However, managers must automatically inherit read and edit access to all vendor dispute records owned by their direct and indirect reports in the role hierarchy. Which configuration of Organization-Wide Defaults (OWD) and sharing behavior satisfies these requirements?

  1. Set the Organization-Wide Default for Vendor_Dispute__c to Private, and ensure Grant Access Using Hierarchies remains checked.Cevap
  2. B
    Set the Organization-Wide Default for Vendor_Dispute__c to Private, and deselect the Grant Access Using Hierarchies option.
  3. C
    Set the Organization-Wide Default for Vendor_Dispute__c to Public Read/Write, and use custom Profiles to restrict record-level view access for non-owners.
  4. D
    Set the Organization-Wide Default for Vendor_Dispute__c to Public Read-Only, and assign a Permission Set to remove record access from peer team members.

Cevap

Set the Organization-Wide Default for the custom object to Private and keep 'Grant Access Using Hierarchies' enabled.
Setting the Organization-Wide Default (OWD) for the custom object to Private restricts baseline record access so that users can only view records they own. Keeping 'Grant Access Using Hierarchies' checked ensures that users higher in the role hierarchy automatically inherit full access to records owned by their subordinates.

Adım Adım Çözüm

1
Determine the baseline record access requirement for standard non-owner users.
Standard users must only access records they own, requiring the most restrictive baseline OWD setting of Private.
Organization-Wide Defaults establish the baseline access level for records users do not own.
2
Determine how access should propagate to management via the role hierarchy.
Enabling 'Grant Access Using Hierarchies' grants managers higher in the role hierarchy the same level of access as record owners.
For custom objects, 'Grant Access Using Hierarchies' is enabled by default, but can be toggled. Keeping it checked ensures automatic upward access propagation.
3
Evaluate whether profile or permission set controls can further restrict access.
Profiles and permission sets grant object and administrative permissions but cannot override OWD to make record-level access more restrictive.
Salesforce security enforces OWD as the absolute base layer of record-level security; sharing tools can only grant additional access, never restrict it.

Anahtar Kavram

Organization-Wide Defaults (OWD) and Role Hierarchy Access
Bu soruyu puanla

Konular

Organization-Wide Defaults (OWD)

Bu konudan daha fazla soru