Territory Management Overview
Territories are groupings of accounts assigned to users. Territory Management enables customers to create territories, assign accounts and users to those territories, and organize those territories into a hierarchical structure. Additionally, Territory Management automatically grants end users visibility to accounts and their related information based on the user's assigned territory. Vault CRM offers several approaches to managing territories based on different business needs:
- Creating Assignment Rules – Accounts automatically associate to territories based on created assignment rules, which can assign accounts based on either their postal code, brick, or other account attributes
- The Account Territory Loader (ATL) – An explicit list of Account-to-Territory assignments that applies to each account, regardless of location
- Manually adding accounts to existing territories
Not all features are available on all platforms. For a list of available platforms for each feature, see Platform Functionality.
Users and Roles
- Territory Managers – Perform the following tasks:
- Creating and Assigning Territories – Territory Managers can create territories and assign accounts and users to them
- Manage automatic Account-to-Territory alignments
- End users – Perform the following tasks:
- Interact with accounts based on their territory
- Manually add accounts to their territory via several other Vault CRM features, including Stakeholder Navigator
Access to Accounts and Related Account Data in Assigned Territories
When an account is assigned to a territory, the account and the following related records are shared with any end user assigned to the territory, as well as any users assigned to territories above the territory in the hierarchy:
- account_merge_history__v
- address__v
- dynamic_attribute__v
- multichannel_consent__v
- product_metrics__v
- territory_fields__v
Permission is granted up to the user's object permission for that object. For example, if a user has Edit permission to the address__v object, the user can edit any address__v records associated with accounts in their territory.
Dynamic Access Control for Territory Management
Dynamic Access Control (DAC) is an access control model in the Vault platform that provides record-level security. Enabling DAC on an object automates the assignment of users to the record’s Viewer, Editor, and Owner roles via Matching Sharing Rules, or customer-defined Custom Sharing Rules.
DAC is especially useful in Vault CRM instances with large numbers of users and records of a certain type of object, for example, enabling DAC on the account__v object to automate account access.
When using DAC , the Share Settings section automatically displays on records of the following objects:
- account_v
- account_merge_history__v
- address__v
- dynamic_attribute__v
- multichannel_consent__v
- product_metrics__v
- territory_fields__v
To ensure proper record-level access, if DAC is enabled on an object that is a child of another object, DAC must also be enabled on the parent object. The following table describes the supported cases for enabling DAC between parent and child objects:
|
Supported Case 1 |
Supported Case 2 |
|
|---|---|---|
|
DAC Enabled on Parent Object |
✔ |
✔ |
|
DAC Enabled on Child Object |
✔ |
✘ |
