To configure this feature:

1. Navigate to Admin > Users & Groups > Permission Sets.
2. Select the appropriate permission set.
3. Select the Objects tab.

4. Grant the following permissions:

   Object	Object Permissions	Object Types	Fields	Field Permissions
   account_territory_loader__v	CRED	n/a	account__v external_id__v territory__v territory_to_add__v territory_to_drop__v	Edit

5. Enter 1 for the atl_mode__v Territory Setting. This step is required for customers using Align and is recommended when using Network or OpenData Delivery Manager.

The following are two methods of processing changes made to ATL records:

• Classic ATL Approach (ATL Mode = 0) – The default setting. Each ATL update or insert updates the account assignments by first clearing each territory assigned to the account and re-inserting only the territories listed in the territory__v field.

• Incremental ATL Approach (ATL Mode = 1) – This approach only processes changes to the territory_to_add__v and territory_to_drop__v fields. Existing territory alignments made via methods other than ATL are not affected.

  Customers using Align must use this approach.

Vault CRM instance can be configured to use one of the approaches via the atl_mode__v Territory Setting.

Classic ATL Processing Approach

The classic processing approach assumes the values listed in the territory__v field are the desired list of territories.

Each ATL insert or update processes the following:

• Territories are added or removed from the territory__v field based on the values of the territory_to_add__v and/or territory_to_drop__v fields. The territory_to_add__v and territory_to_drop__v fields are then cleared. The territory__v field can also be updated directly without using the territory_to_add__v or territory_to_drop__v fields.
• All manual territory assignments are deleted
• New territory assignments are created for each territory listed in the territory__v field

Incremental ATL Processing Approach

For some Vault CRM environments, the classic approach adversely affects Account Territory assignments from other alignment methods by deleting valid territory assignments not listed on the ATL record.

This is especially true for territory assignments that come from outside of Vault CRM, for example, from Veeva Align. Some of these systems do not use ATL for Territory Management. The incremental processing approach enables continuing to use the ATL in conjunction with outside assignment systems that do not use ATL.

Each ATL insert or update processes the following:

• Territories are added or removed from the territory__v field based on the values of the territory_to_add__v and/or territory_to_drop__v fields. The territory_to_add__v and territory_to_drop__v fields are then cleared.
• The existing values in the territory__v field are compared to the changes made from the Add or Drop fields. Only differences are processed.

For example, a user aligned to Territory 103 uses Network Account Search to add an account to their territory, resulting in an upserted ATL record. Only Territory 103 is listed in the territory__v field on the account_territory_loader__v object in Vault CRM. Because the atl_mode__v field is set to 1, ATL does not delete the initial two territories inserted by Align (101 and 102). The ATL processing approach processes only the single Territory listed in the ATL record—Territory 103.

Vault CRM environments with Veeva Align managing the Territories and account assignments must have the atl_mode__v Territory Setting set to 1.

While account_territory_loader__v records can be manually created in Vault CRM, the most common way to add or edit these records is data loading via the Vault Loader.

Each account should only have one associated ATL record.

The following are basic recommendations when data loading ATL records.

Inserting ATL Records

When account_territory_loader__v records are created, populate the following fields:

• account__v
• external_id__v
• territory__v – Populate this field when using the Classic ATL Approach (ATL Mode 0)
• territory_to_add__v – Populate this field when using the Incremental ATL Approach (ATL Mode 1)

Updating ATL Records

Updating or Upserting existing account_territory_loader__v records should include the following fields:

• account__v
• external_id__v
• territory__v – Used in the Classic ATL Approach (ATL Mode 0). A semicolon-delimited list of territory API names to assign to the account.
• territory_to_add__v – Used in the Incremental ATL Approach (ATL Mode 1). A semicolon-delimited list of territory API names to add.
• territory_to_drop__v – Used in the Incremental ATL Approach (ATL Mode 1). A semicolon-delimited list of territory API names to drop.

When updating account-to-territory assignments, end user visibility to accounts processes asynchronously. This means a delay can be expected when updating assignments for multiple accounts.