Apr 29, 2019 | 0 Comment | Posted by Shrey Sharma

Role Hierarchy

Every Salesforce organization maintains a role hierarchy for the organization using Salesforce.
This role hierarchy defines the hierarchy of the users working in the organization.

 

Role Hierarchies can be used to extend the record access automatically so that:

  • A Manager will always have access to the same data as his/her employees regardless or the org-wide defaults settings.
  • Users who tend to need access to the same types of records can be grouped together. (These groups can be used as Roles & Sub-Ordinates in Sharing Rules).

 

Role hierarchies don’t have to match your org chart exactly. Instead, each role in the hierarchy should just represent a level of data access that a user or group of users need.

Depending on organization’s sharing settings, roles can control the level of visibility that users have into organization’s data. Users at any given role level can view, edit, and report on all data owned by or shared with users below them in the role hierarchy, unless organization’s sharing model for an object specifies otherwise.

Note: If the “Grant Access using Hierarchies” option is disabled for a custom object then only record owner and users granted access by the org-wide defaults have access to object’s records. However users such as with the “View All” and “Modify All” object permissions and the “View All Data” and “Modify All Data” system permissions can still access records they do not own.

“Grant Access using Hierarchies” option is enabled for all objects and it can only be changed
for custom objects.

Public Groups

A public group consists of a set of users. It can contain individual users, other groups or the users in a particular role or territory plus all the users below that role (subordinates) in the hierarchy.

Here is where you can learn about Sharing Rules.

Share This Post

Leave a Comment

Your email address will not be published. Required fields are marked *