The CRM Team Hierarchy builds your hierarchy, based on your CRM, to show a manager's individual data broken out from how the whole team is performing, in addition to overall team performance. This allows for simpler roll ups, custom inclusion of a team lead's numbers as a member of the team, and easier goal setting to match your organization's hierarchy.
Check out the configuration and examples below.
Team Hierarchy Configuration Options
show only teams and users in the hierarchy that a user is authorized to view: this allows you to determine whether the hierarchy is visible to everyone or is based on group authorizations
Default Root Node: determines the root node of the hierarchy (is it your CEO? someone else? who does everyone fall under?)
Include the managers as a member of their own team: THIS is the main purpose of a team hierarchy that allows you to determine whether a manager is only the manager of their team or also a member of the team (this will be very important in how you set goals!)
Exclude nodes and their subordinates: enter any nodes that should be excluded from the hierarchy, eg. an Ops team that doesn't access this data or set goals can be excluded so the hierarchy only shows the users you want visible
Exclude users from the hierarchy: you can also exclude individual users from the hierarchy
Below we have elected to "include the managers as a member of their own team" so you can see that the manager, Jessica Campos is listed as the leader (Jessica Campos' Team) and Jessica is also listed as a member of her own team.
In the scenario below we have NOT elected to "included the managers as a member of their own team" so you can see that while Jessica is still the manager of her team (Jessica Campos' team) she is NOT listed as a member of her own team. You can Jessica listed individually as a member of her own managers team, but not her own.
If you run into any issues, please contact support.
Please sign in to leave a comment.