You are here:
Organizational Hierarchies in Tableau Semantics (Beta)
Organizational hierarchies reflect your company's reporting structure — who reports to whom and how teams are organized — and let analysts and business users analyze metrics at any level of that structure in Tableau Semantics. Without organizational hierarchies, each organizational level requires a separate metric definition.
Required Editions
In Tableau Semantics, you can add an organizational hierarchy from your Salesforce org ingested into Data 360 into your semantic model. The analysts and business users use this data to analyze metrics at any level of your org's structure.
With organizational hierarchies, you can answer critical business questions like "What's my team's revenue?" or "How is my region performing?" without creating separate metric definitions for each organizational level.
When you add an organizational hierarchy to your semantic model, Tableau Semantics enables two key capabilities for your users:
- Automatic rollup/drill-down: Aggregate data at any organizational level and drill from summaries to individual details.
- Personalized analysis: Each user sees metrics relevant to their position in the hierarchy.
Organizational hierarchies are configured at the Salesforce org level and represent your company's structure. Tableau Semantics supports two hierarchy types:
- Role hierarchy: Defines which roles report to other roles in your organization.
- Manager hierarchy: Defines the direct manager-to-employee reporting relationships based on the Manager field on user records.
For more information on organizational hierarchy types, see Organizational Hierarchy Types and Structures (Beta).
| Available in: All editions supported by Data 360. See Data 360 edition availability. |
Prerequisites
-
Before using organizational hierarchies in Tableau Semantics, turn them on in any of these locations in your org:
- Data Cloud Setup > Feature Manager
- Data Cloud Setup > Tableau Next Features
- Tableau Next workspace settings
-
Configure hierarchies in Salesforce: Set up at least one organizational hierarchy (Role or Manager) in your Salesforce org User settings.
- Role hierarchy: See Create a User Role.
- Manager hierarchy: See Assign Managers for Users.
- Set up a Salesforce CRM connector: Before ingesting data, configure a Salesforce CRM connector to connect your Salesforce org to Data 360. For more information, see Data Governance and Sharing in Tableau Next and Salesforce CRM Connector.
- Ingest hierarchies into Data 360: Configure Data 360 to ingest the organizational
hierarchies from your Salesforce org. This populates hierarchy logic in the User and
UserRoleData Model Objects (DMO). For more information, see Ingest Hierarchical Data. - Confirm that the organizational hierarchy option is available: In your semantic model, click New and verify that Organizational Hierarchy is listed. You can then add it as a logical view object in the semantic model.
Auto-Generated Fields
When you add an organizational hierarchy to your semantic model, Tableau Semantics autogenerates several fields that enable drill-down, roll up, and hierarchy-based filtering. These fields are system-generated and can’t be manually edited or deleted. The specific fields created depend on which hierarchy type you select.
The tables below list the fields generated for each hierarchy type.
Manager Hierarchy Auto-Generated Fields
| Field Name | Description | Visibility | Example |
|---|---|---|---|
| User Hierarchy | ID path through the management chain | Visible | 005UA00000119YjYAI|006UA00000119YjYBY |
| Username Path | Full chain of usernames | Hidden by default | Sarah Chen (CEO) | Michael Rodriguez (VP Sales) |
| User Level | Position in the management tree, numbered from the top down (Level 1 = CEO, Level 2 = VP, and so on) | Visible | 2 |
You can also add optional fields from the User DMO when configuring the hierarchy, such as Full Name, User Id, Manager, and custom user fields configured in your org.
Role hierarchy Auto-Generated Fields
| Field Name | Description | Visibility | Example |
|---|---|---|---|
| User Hierarchy | User ID path through the user chain. Experiences such as Tableau Next use this field for hierarchy-based filtering, drill-down, and roll-up. | Visible | 005A001/005B002/005C003/005D004 |
| Role Hierarchy | Role ID path | Visible | 00E001/00E002/00E003/00E004 |
| Role Name Path | Full chain of role names | Hidden by default | CEO/VP Sales/West Region Manager/Sales Rep |
| Role Level | Depth in role hierarchy | Visible | 3 (Level 1 = CEO, Level 4 = Rep) |
You can also add additional optional fields from the UserRole DMO when configuring the hierarchy, such as Full Name, User Id, Parent Role, and custom user fields configured in your org.
Use Cases
Organizational hierarchies allows users filter metrics and measures by any team in the organizational hierarchy. Instead of building separate "rep revenue," "manager revenue," and "VP revenue" metrics, you define a metric once and let users filter it by team.
- Sales Management
A single "Sales" metric serves an entire sales org, and users can filter it by role to see the numbers for any team in the hierarchy.
- A VP of Sales filters the Sales metric by "My Team" and sees the pipeline rolled up from every manager and rep beneath them as one combined total.
- A sales rep can filter any hierarchy-enabled metric to their level in the hierarchy to see their team’s or other team’s performance across metrics, dashboards, and visualizations.
- Tableau Agent
When a semantic model includes an organizational hierarchy, it enables an agent to return hierarchy-aware answers.
- A regional manager asks "What's my team's ACV this quarter?" and gets a figure that automatically includes every subordinate below them in the hierarchy, not the whole company, and not just their own deals.
- Because the scoping comes from the semantic model, two people asking the identical question get correctly different answers: the VP's "my team" spans the full region, while a rep's "my team" is just themselves.
- Executive Dashboards
Hierarchies power dashboards that read top-down and let viewers drill into detail.
- A CEO dashboard shows company-wide sales at the top (Level 1), then lets the CEO drill down through Level 2 (VP Sales, VP Engineering) to Level 3 managers (EMEA, APAC) and into individual contributors. Each level's total is the sum of everyone beneath it.
Limitations
The following limitations apply to organizational hierarchies in Tableau Semantics:
- The My Team filter isn't supported in Personal orgs. Queries that use this filter return empty results. As a workaround, filter by the logged-in user's team, which appears in the filter picker list.
- You can't filter the hierarchy logical view inside the semantic models.
- When you query the User_Hierarchy field together with a measure, Tableau Semantics aggregates the results by role or team, not by individual user.
- The Metric insights based on hierarchy reasoning aren't supported.
- The available hierarchy filters in Tableau Next are Me & My Team, which includes you and all subordinates in the hierarchy. Filtering by Me as an individual isn't available yet.
- Organizational Hierarchy Types and Structures (Beta)
Tableau Semantics supports two organizational hierarchy types — Manager Hierarchy and Role Hierarchy — each of which aggregates data differently and determines the scope of 'My Team' filtering for your users. - Add an Organizational Hierarchy to a Semantic Model (Beta)
Add an organizational hierarchy to your semantic model to answer hierarchy-related analytics questions across your company's reporting structure such as "What's my team's revenue?" or "How is my region performing?", without requiring separate metric definitions for each level. - Add Hierarchy Filters to Metrics (Beta)
After you add an organizational hierarchy to your semantic model, hierarchy levels become available as filter dimensions when you create or edit metrics, letting you scope a metric to specific branches of your organizational structure. - Add Hierarchy Filters to Sub-Metrics (Beta)
Use sub-metrics to provide additional granularity and track more detailed performance indicators scoped to specific teams or reporting lines in your organizational hierarchy.
