Universal Containers wants its Field Sales team to only see the accounts that they own. Separate North American and European marketing teams should only see accounts in their respective regions. The Inside Sales Team needs to see all accounts in Salesforce.
How should an app builder accomplish this?
To meet the requirements, the Organization-Wide Default (OWD) for accounts should be set to Private to restrict access to only the owners of the records by default. Criteria-based sharing rules can then be created to grant access to the specific accounts for the respective North American and European marketing teams, ensuring they only see accounts within their regions. For the Inside Sales Team, a profile with the 'View All' setting for accounts ensures that they can see all accounts in Salesforce. This approach ensures that access is appropriately restricted and shared based on roles and regions.
Shouldn't this be D?
Should be D
Why not C? Because permission set is used for Object and field level security. Sharing Rule is used for records. https://help.salesforce.com/s/articleView?id=sf.security_data_access.htm&type=5
It is D, for sure.
Answer is D. Here we need to restrict records, so definitely can't be B
I think D , OWD should not be Public ,so can create sharing rule fot it
OWD needs to set to private in order to have the control over the sharing rules
D is correct
Should be D
D is the correct answer
Should be D
Its C, sure
They are asking to control the record access. So, the permission set can't handle the record restriction.
Answer is D.
D is correct as the OWD needs to be set to private.
It is D.
Answer is D. OWD needs to be private then sharing used to control who sees what.
Using permission sets instead of criteria-based sharing rules is not the best practice for region-based access control. Criteria-based sharing rules are more suitable for this purpose.