Opportunities Visibility and Account Creation
Question
The sales director at Cloud Kicks does not want users viewing each other's Opportunities, but wants users to check to see that the Account does not already exist prior to creating a new Account.
Which Organization-Wide Default should the Consultant recommend?
Answers
Explanations
Click on the arrows to vote for the correct answer
A. B. C. D.B
To address the sales director's requirements at Cloud Kicks, the consultant should recommend the Organization-Wide Default (OWD) settings for Salesforce. The goal is to prevent users from viewing each other's Opportunities while ensuring they can check if an Account already exists before creating a new one. Let's evaluate each option and determine the most suitable recommendation:
A. Set Account to Public Read Only, and Opportunity to Public Read Only: This option allows all users to view all Accounts and Opportunities, which doesn't meet the requirement of restricting users from viewing each other's Opportunities.
B. Set Account to Public Read/Write, and Opportunity to Private: In this option, while the Account can be created and edited by all users, the Opportunities are set to private. This fulfills the requirement of users not being able to view each other's Opportunities. However, it doesn't address the need to check if an Account already exists before creating a new one.
C. Set Account and Opportunity to Private: Setting both the Account and Opportunity to private would restrict access to both objects. It doesn't fulfill the requirement of allowing users to check if an Account already exists before creating a new one.
D. Set Account to Public Read Only, and Opportunity to Controlled by Parent: This option sets the Account access to Public Read Only, allowing users to view the Account records. However, the Opportunity access is set to Controlled by Parent, which means the visibility and access to Opportunities will be determined by the sharing settings of the associated Account. This aligns with the requirement of preventing users from viewing each other's Opportunities.
Therefore, the recommended Organization-Wide Default setting is: D. Set Account to Public Read Only, and Opportunity to Controlled by Parent.
By implementing this setting, users at Cloud Kicks will be able to view Account records (to check if an Account already exists) while having restricted access to Opportunities, ensuring they cannot view each other's Opportunities.
