![]() ![]() When creating a role hierarchy, it's probably easiest to stick with this or the list view, because they both make it easy to see how the roles all fit together in the hierarchy. The default view for this page is the tree view, as indicated in the drop-down list on the far right side of the Role Hierarchy title bar. If you see an introductory splash page called Understanding Roles, click Set Up Roles at the bottom of the page to skip to the actual tool. From Setup, in the Quick Find box, enter Roles, and then select Roles.Once that’s done, you can get started defining the role hierarchy itself. Deselect Grant Access Using Hierarchies if you want to prevent users from gaining automatic access to data owned by or shared with their subordinates in the hierarchies.įor example, if a software development group has a staff software engineer and a junior software engineer, these positions can be consolidated into a single Software Engineer role in the hierarchy. In the Organization Wide Defaults section, click Edit. To control sharing access using hierarchies for any custom object, enter Sharing Settings in the Quick Find box and select Sharing Settings. ![]() It can only be changed for custom objects. By default, the Grant Access Using Hierarchies option is enabled for all objects. For example, the role hierarchy automatically grants record access to users above the record owner in the hierarchy. Specifically, in the Organization-Wide Defaults related list, if the Grant Access Using Hierarchies option is disabled for a custom object, only the record owner and users granted access by the org-wide defaults receive access to the object's records.īeyond setting the org-wide sharing defaults for each object, you can specify whether users have access to the data owned by or shared with their subordinates in the hierarchy. 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 your sharing model for an object specifies otherwise. We'll use these groups later when we talk about sharing rules.ĭepending on your sharing settings, roles can control the level of visibility that users have into your Salesforce data. Users who tend to need access to the same types of records can be grouped together.A manager always has access to the same data as his or her employees, regardless of the org-wide default settings.Each role in the hierarchy just represents a level of data access that a user or group of users needs. But role hierarchies don't have to match your org chart. Users who need to see a lot of data (such as the CEO, executives, or other management) often appear near the top of the hierarchy.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |