---
schema_version: "1"
id: e3ff2a0093a10c1c79350e2ac86ee83461b1169052018600d8ac043c7af7d105
title: Control Access to Data Based on a User’s Assigned Territories (Generally Available)
collection: admin
version: current
locale: en-us
portal_url: https://docs.salesforce.com/admin/current/en-us/release-notes/260-0-0/rn_bi_integrate_territory_hierarchy_security_predicates_ga.md
canonical_url: https://help.salesforce.com/s/articleView?id=release-notes.rn_bi_integrate_territory_hierarchy_security_predicates_ga.htm&release=260&type=5
source_site: help.salesforce.com
content_type: documentation
content_hash: 10edd5ae77914298556b2642fff0833fc71be4ba84f0b25730c846f27cb77cb1
description: Allow users to see data in dashboards and insights only for the territories they’re assigned to in Territory Management 2.0. Reference the territory hierarchy from your dataset security predicates. Previously, you could only reference user data. This feature is now generally available.
products:
  - Cross Cloud Packages Solutions
release: "260"
---
# Control Access to Data Based on a User’s Assigned Territories (Generally Available)

Allow users to see data in dashboards and insights only for the territories they’re assigned to in Territory Management 2.0. Reference the territory hierarchy from your dataset security predicates. Previously, you could only reference user data. This feature is now generally available.

**Where:** This change applies to CRM Analytics in Lightning Experience and Salesforce Classic. CRM Analytics is available for an extra cost in Enterprise, Performance, and Unlimited editions.

**How:** In the recipe or dataflow that defines the dataset, add a flattened territory hierarchy (multivalued dimension) for each row. For example:

![Table showing the required territory hierarchy data needed in a dataset.](https://sf-zdocs-cdn-prod.zoominsoftware.com/tdta-salesforce_release_notes-260-0-0-production-enus/ba62a63b-6cd1-440e-8d24-e867afab0363/salesforce_release_notes/images/analytics/rn_bi_integrate_territory_hierarchy_security_predicates_dataset.png)

Then, include this security predicate filter in the output node:

```
‘Territory2.TerritoryIDs’ in [“$UserTerritory2Ids”]:
```

#### See Also

- [_Salesforce Help_: Sales Territories](https://help.salesforce.com/s/articleView?id=sales.tm2_intro.htm&language=en_US)
- [_Salesforce Help_: Add Row-Level Security with a Security Predicate](https://help.salesforce.com/s/articleView?id=analytics.bi_security_datasets_predicate_considerations.htm&language=en_US)
- [_Salesforce Help_: Row-Level Security Example based on Territory Hierarchy](https://help.salesforce.com/s/articleView?id=analytics.bi_security_rowlevel_example_territoryhierarchy.htm&language=en_US)