Organizational Hierarchy Types and Structures (Beta)

Filtering by "My Team" shows all users below you in the hierarchy. The scope depends on which hierarchy type your org uses:

• Manager Hierarchy: Your direct and indirect reports
• Role Hierarchy: All users in subordinate roles

Manager Hierarchy

Manager Hierarchy uses manager/report assignments from user profiles where each person has one manager (or none if top-level). Use this hierarchy for people analytics, HR reporting, and org charts. The "My Team" filter returns all your direct and indirect reports.

Auto-Generated Fields

Tableau Semantics auto-generates the following fields:

• User Hierarchy: ID path through the management chain
• Username Path: Name path through the management chain (hidden by default)
• User Level: Depth in the management tree

You can also add additional optional fields from the User DMO when configuring the hierarchy.

Example: Manager Hierarchy with 3 Levels

Org Structure:

• Level 1: Sarah Chen
• Level 2: Michael Rodriguez
• Level 3: Robert Martinez

Auto-generated fields for Robert Martinez:

• User Hierarchy: 005UA00000119YjYAI | 005UA00000... | 005UA00000...
• User Name Path: Sarah Chen | Michael Rodriguez | Robert Martinez (hidden by default)
• User Level: 3

When Michael Rodriguez filters a metric by "My Team," he sees aggregated data for the managers who report to him, such as Robert Martinez. When Sarah Chen filters by "My Team”, she sees data for Michael, Robert, and everyone below them rolled up.

The following image shows a visualization using the Manager hierarchy: Level 1, Level 2, and Level 3 in rows with SUM(Sales), filtered by User Hierarchy. Sales roll up from individual managers to the CEO.

Role Hierarchy

Role Hierarchy uses role assignments from user profiles where each role has a parent role (or none if top-level). This hierarchy follows your organization's job titles and positions as defined in Salesforce Role Hierarchy. Use this for sales analytics, sales pipeline and quota rollup, forecasting, and revenue reporting where data visibility should follow role structure.

Role Hierarchy Structures

Role Hierarchy comes in two structural variations depending on how your org assigns roles:

• Single User per Role: One person per position
• Multi User per Role: Multiple people share the same role

When using "My Team" filtering, the results include all users in roles beneath yours in the hierarchy.

Auto-Generated Fields

Tableau Semantics auto-generates the following fields:

• User Hierarchy: User ID path through the management chain
• Role Hierarchy: Role ID path through the role chain
• Role Name: Name path through the role chain (hidden by default)
• Role Level: Depth in the role tree

You can also add additional optional fields from the UserRole DMO when configuring the hierarchy.

Example: Role Hierarchy with 3 Levels

Org Structure:

• Level 1: Sarah Chen (CEO)
• Level 2: Jennifer Kumar (VP Engineering) and Michael Rodriguez (VP Sales)
• Level 3: Robert Martinez (Manager EMEA) and Thomas White (Manager APAC), both under VP Sales

Auto-generated fields for Robert Martinez (Manager EMEA):

• User Hierarchy: 005UA00000119YjYAI | 005UA00000... | 005UA00000...
• Role Hierarchy: ID path through the role chain (CEO → VP Sales → Manager EMEA)
• Role Name: Manager EMEA
• Role Level: 3

When Michael Rodriguez (VP Sales) filters a metric by "My Team," he sees aggregated Sales for the roles beneath him: Manager EMEA and Manager APAC. When Sarah Chen (CEO) filters by "My Team," Sales roll all the way up: her total combines VP Sales, VP Engineering, and every manager below them.

In the "Role - Levels drilldown by Sales" visualization, Level 1, Level 2, and Level 3 appear as rows with SUM(Sales) in columns. Sarah Chen's Level 1 bar (~2M) equals the sum of all roles below her, while each manager's bar shows only their own contribution.