A company has a private sharing model in place and one of the sales users is having issues in accessing a type of record they need.
This sales user is located at the bottommost of the role hierarchy.
What is the best approach to give the user access?
Click on the arrows to vote for the correct answer
A. B. C. D.Correct Answer: C
Use sharing rules to extend sharing access to users in public groups, roles, or territories.
Sharing rules give particular users greater access by making automatic exceptions to your org-wide sharing settings.
You can do this based on a sharing rule on record ownership or other criteria.
After you select which records to share, you define which groups or users to extend access to and what level of access they have.
Option A is incorrect because the role hierarchy automatically grants record access to users above the record owner in the hierarchy.
Option B is incorrect because field level security controls whether a user can see, edit, and delete the value for a particular field on an object.
Option D is incorrect because organization wide default is baseline settings in Salesforce which specify which records can be accessed by which user and in which mode.
In this scenario, the sales user is at the bottommost of the role hierarchy and is facing issues accessing a specific type of record. The company has a private sharing model in place, which means that only the record owners and users with appropriate access permissions can view or modify the records.
To provide the sales user with access to the required records, the best approach would be to use sharing rules.
Sharing rules allow administrators to extend record access to users in public groups, roles, territories, or based on the criteria defined in the rule. By defining sharing rules, you can grant read or edit access to a group of users without changing their roles or profiles.
In this scenario, the sales user is located at the bottom of the role hierarchy, and granting them access through role hierarchy may not be feasible or practical. Moreover, field level security controls the visibility and editability of fields, which may not be relevant in this case.
Organization-wide defaults are used to set the baseline level of access for all users in the organization. Changing organization-wide defaults may lead to unintended consequences and may not be the best approach to address the issue faced by the sales user.
Therefore, the best option in this scenario is to use sharing rules to extend access to the required records to the sales user. Sharing rules can be based on criteria such as record owner, record type, or field values, and can be created and managed by administrators in Salesforce.