SHARING-AND-VISIBILITY-DESIGNER practice question 17 of 30

Universal Containers would like to control access to records and objects according to the following business requirements:• Sales users can view all…

Full set: 212 questions
Universal Containers would like to control access to records and objects according to the following business requirements:• Sales users can view all Account records but only edit their own records. • Sales managers view all Account records but only edit records of the team. • Service users can view all Account records that are not marked with a RecordType of Prospect. Which organization-wide default configuration should a Salesforce architect recommend to fulfill these requirements?
Answer options
A: Public Read Write
B: ​Private Correct answer
C: Public tad Only
D: Public Read/Transfer
Correct Answer:
B. ​Private
Explanation

The requirements necessitate starting with the most restrictive Organization-Wide Default (OWD). Setting the Account OWD to Private ensures that, by default, users can only access records they own. This baseline allows for granular access to be opened up. A sharing rule can then be created to grant all Sales and Sales Manager users read-only access to all accounts. A second, criteria-based sharing rule can grant Service users read-only access only to accounts where the RecordType is not 'Prospect'. This configuration is impossible with a Public Read Only OWD, as you cannot use sharing rules to restrict access that the OWD has already granted.

Why Incorrect

A. Public Read/Write would allow sales users to edit all accounts, violating the requirement that they only edit their own.
C. Public Read Only would grant Service users access to all accounts, including 'Prospect' types, which cannot be restricted with sharing rules.
D. Public Read/Transfer is not a valid sharing setting for the Account object. The setting is Public Read/Write/Transfer.

References

1. Salesforce Help. (2023). Organization-Wide Sharing Defaults. "The first step in this layered sharing model is to determine the organization-wide defaults for each object... set the default to the most restrictive level."

2. Salesforce Help. (2023). Sharing Rules. "Sharing rules are used to extend sharing access to users... They are not used to restrict access to records." This confirms why a Public OWD would fail requirement #3.

3. Salesforce Architects. (2023). Designing Record Access for Enterprise Scale. "The Organization-Wide Default (OWD) setting specifies the baseline level of access that a user has to records they do not own... From this baseline, you can open access back up."

Scroll to Top