A Territory, which is the customer group or area a user is responsible for, is the focal point for the entity assignments required by CRM and reporting. In CRM, the user is the focus; in Align, the Territory is the focus. Territories are applicable for all lines of business, profit centers, and cost centers; from sales to medical field personnel.

The following table contains descriptions for Territory fields: 

Only alphanumeric characters and underscores are supported.

Field Description
Start Date & End Date

Indicates the date range of the Territory's life. The Start and End Dates of assignments must fall within this date range.

Do not extend the End Date value if the current end date is in the past. Instead, create a record.

Effective Date/Time

Indicates when the record became applicable to CRM. For example, a Territory's parent is called San Francisco Diabetes through December 31 and became Los Angeles Diabetes the following January 1. The Territory’s Effective Date/Time for the parent change is January 1 at midnight.

The effective Date/Time must fall between the parent Territory’s Start & End Dates.

External ID (Optional) Is the Territory ID the customer uses in internal systems
Hierarchy Level

A configurable level within the reporting structure. No constraints based on the Parent Territory's Hierarchy Level. Typically, Territory is the lowest level.

Parent Territory (Optional) The territory that is directly above this one in the territory hierarchy. This is used to build coherent territory trees for organizational purposes.
Field Force (Optional) The functional team that this territory is assigned to.
Country (Optional) The country assigned to the Territory.
Send to CRM

Yes” indicates the Territory is sent to CRM

This field is pre-populated with the Parent’s Send to CRM value

If the Parent’s Send to CRM = No, the Territory’s value can be changed to Yes

Veeva CRM Org

If the parent Territory has a Veeva CRM Org value populated, the child Territory’s Veeva CRM Org field is auto-inherited and it cannot be changed.

If the parent Territory does not have a Veeva CRM Org value, this field is editable and is dependent on Sent to CRM.

Changing a Parent Territory’s Veeva CRM Org value, or Send to CRM to Yes, initiates a process to apply the same change to the subordinate Territories. This change branches out through all Territory levels below the Parent in the hierarchy. Changing the Parent’s Send to CRM to No does NOT branch down to subordinate Territories.

CRM Account Access

When sent to CRM, the selected value is stored on the CRM field: Territory.AccountAccessLevel

It controls the Account access the user assigned to the Territory has for all assigned Accounts

This setting can override what a CRM User’s Profile has for the Account object. For example if the CRM Profile has Edit for the Account object but the Territory AccountAccessLevel = ReadOnly, then the Accounts in that Territory are read-only.

The objects referenced by Territory are: territory__aln (for Parent Territory), field_force__aln, country__aln, and veeva_crm_org__aln.

The Territory entity has a list and detail view, and is accessible from the Entities tab. Territory can be created, edited, and deleted manually via the UI. The same actions can be done using the delimited import process. If designated, it is pushed to Veeva CRM.

The Territory detail view includes a related list section for:

  • Roster Member Assignment
  • Child Territories
  • Account Assignment
  • Field Force Rule Assignment
  • Rule Assignment
  • Geography Assignment
  • Product Assignment

Territory displays as a related list assignment on the following detail views: Field Force, Roster Member, and Account.