---
sourceDocument: Australia Platform Analytics
sourceDocumentLink: https://www.servicenow.com/docs/r/now-intelligence

 Release :

    - australia

ft:locale :

    - en-US

ft:publication_title :

    - Australia Platform Analytics

ft:clusterId :

    - par

bundleId :

    - par

workflow :

    - Platform


---

# Create a hierarchical filter

# Create a hierarchical filter {#ariaid-title1}

* Release version: Australia
* 
* Updated March 12, 2026
* 
* ![](https://www.servicenow.com/docs/portal-asset/ico-clock) 3 minutes to read

If a record hierarchy is defined for a table that is used as a filter source, you can create a single or multiple select filter that follows that hierarchy. The Manager hierarchy on User \[sys_user\] is the typical use
case.

## Before you begin

This procedure requires you to have created a filter and started to configure it as a single or multiple select filter.

Role required: In the inline dashboard editor: dashboard_admin, or you must be the dashboard owner or have had editing rights shared with you.

In the Filter Designer (LibraryFiltersNew): analytics_filter_admin or higher

## About this task

A record hierarchy consists of a parent record and all child records where a reference field value defines parent-child relationships. For example, in the Manager hierarchy, this field is the Manager field on the User
\[sys_user\] table. One user is the parent, and all users who have that user specified in the Manager field are child records. The hierarchy is multi-generational, so to speak, so users with a Manager who have the parent as
their Manager are also included in the hierarchy. In short, starting with one manager, that manager's entire downward reporting chain is included in the hierarchy.

When you filter through a record hierarchy, you select one value of the reference field to be the parent. You can then filter by that value and/or by any of its child values.  
Note:  
Hierarchical filters support only the hierarchies defined in the Record Hierarchy \[sys_record_hierarchy\] table and not those defined in other tables, such as Governance, Risk, and Compliance (GRC) tables. Hierarchical filters generally follow the same logic as hierarchical queries, as described in [Building hierarchical queries](https://www.servicenow.com/docs/access?context=data-hierarchies&version=australia&pubname=australia-platform-administration&ft:locale=en-US).

To create a hierarchical dashboard filter, follow the procedure in [Configure a Single/Multiple select or cascading filter](https://www.servicenow.com/docs/RLvttlx0xmUgN51EJkD4hg "Let users filter a dashboard tab on one or more values from a set of choices, such as incident priority. You can have a single or multiple select filter follow another filter in a cascade.") to create a multi-select filter. When you reach the step where you define the filter source, specify the hierarchy.

## Procedure

1. Create a filter and select the Single or Multiple Select filter type, as described in [Create or add a filter on an inline dashboard](https://www.servicenow.com/docs/EgipF0if1yb5FCroSh3bHw "Create a filter or select one from the filter library. When creating a filter, name it, and choose whether to create a single select, multiple select, date, or true/false filter.") or [Create a filter in the Filter Designer](https://www.servicenow.com/docs/H1MeS2i6mEkpi6rSEuMV5A "Create a Platform Analytics filter in the Filter Designer and add it to the library for reuse.").
2. Select a Table source.  

   <br />

3. Select a table that has a record hierarchy, such as User \[sys_user\].
4. Do not select a table field.
5. Select Is in hierarchy.
6. In Select record hierarchy, select from among the record hierarchies defined for this table.  
   Most tables have no more than one record hierarchy.
7. In the Select starting at field, select the top-level value in the hierarchy for the purposes of this filter.  
   The values to select in the filter will be this value and all its child values.
8. Select Apply.
9. When you select the data to filter, select a field in the same table as the filter source or a reference field that points to the same table as the filter source.  
   Note:  
   The filter also applies to visualizations of native Data snapshots indicators that have that table specified in their Data snapshots source. For more information, see [Create a Data snapshots source](https://www.servicenow.com/docs/XA3HO4rCirSi_KzfbwlYCQ "To provide a filtered dataset of records that you can evaluate with one or more indicators, create an indicator source. Data snapshots indicators require different sources than do classic indicators. Data snapshots logs are accessible on the source records.").
10. Complete configuring the filter as described in [Configure a Single/Multiple select or cascading filter](https://www.servicenow.com/docs/RLvttlx0xmUgN51EJkD4hg "Let users filter a dashboard tab on one or more values from a set of choices, such as incident priority. You can have a single or multiple select filter follow another filter in a cascade.").
{#create-hierarchical-filter__ol_h1j_hbq_1hc}

## Filter on the Manager hierarchy {#create-hierarchical-filter__example_ilk_grq_1hc}

In your company, you have a manager named Fred Luddy. He has one direct report named Beth Anglin.  

Beth in turn has one direct report named Bradly Hasselvander.  

You want a dashboard where the viewer can choose to see the details of indicators owned by anyone in Fred Luddy's reporting chain. You design a dashboard with some relevant data visualizations, and then you add a Multiple Select filter. You select the User table as the source, turn on Is in hierarchy, and specify the Manager hierarchy starting with Fred Luddy.  

For the data to filter, you select Incident.Assigned to, which is a reference field pointing to User.  

The end result on the dashboard is a filter that can filter by Fred Luddy, Fred's direct report Beth Anglin, or Beth's direct report Bradly Hasselvander.  

*[\>]: and then