Universal Container's Salesforce Admin set the organization wide default for the account object to private and the role hierarchy is enabled.
Later, another request came from the sales VP to open access to another role that is not on the role hierarchy tree division or branch? What would the Salesforce Admin do to extend the access?
Click on the arrows to vote for the correct answer
A. B. C. D.Correct Answer: D
Sharing rules can be used to extend access to roles.
Sharing rules can be used to extend access to roles, roles and subordinates, public groups or for a manager of a group or the subordinate group manager or sharing files can be used to provide access based on the record criteria.
So, through sharing rules, you have two options to extend the access - there is the record owner or the record criteria.
Option A is incorrect because manual sharing provides sharing for one user.
Option B is incorrect because permission set cannot be assigned to a role.
Option C is incorrect because field level security is used to restrict access to a field.
Reference:
The scenario presented involves Universal Container's Salesforce Admin setting the organization wide default for the account object to private and enabling the role hierarchy. Later, the Sales VP requests access to be extended to another role that is not on the role hierarchy tree division or branch.
To grant this access, the Salesforce Admin can use the following methods:
A. Manual Sharing: This method allows a record owner or someone with the "Manage Sharing" permission to manually share a record with another user or role. In this case, the Salesforce Admin can locate the specific account record that needs to be shared and manually grant access to the specific role requested by the Sales VP.
B. Permission Set: A permission set is a collection of settings and permissions that can be assigned to users to grant them additional access to certain features or data. In this case, the Salesforce Admin can create a permission set that includes the necessary access to the account object and assign it to the specific role requested by the Sales VP.
C. Field Level Security: Field-level security allows administrators to restrict access to specific fields on an object, controlling which users can see and edit certain fields. In this case, the Salesforce Admin can use field-level security to grant access to specific fields on the account object to the specific role requested by the Sales VP.
D. Sharing Rules: Sharing rules allow administrators to automatically extend access to records based on specific criteria, such as a user's role or record ownership. In this case, the Salesforce Admin can create a sharing rule that grants access to the specific role requested by the Sales VP based on certain criteria, such as a specific record type or geographic location.
In summary, the Salesforce Admin can use any of the above methods to extend access to the specific role requested by the Sales VP, depending on the specific requirements and circumstances.