Source: https://vaultcrmhelp.veeva.com/doc/Content/CRM_topics/Align/UserMgmt/PrimaryTerr.htm ## Designating a Primary Territory To determine incentive compensation credit for territory assignments in downstream systems, establish clear territory responsibilities, and resolve integration conflicts that may occur when a user is assigned to multiple territories, Align admins can designate a territory as being a roster member’s primary territory. Primary territories are prioritized when Align configures a user in CRM using setup data inherited from their functional profiles, but the user is assigned to multiple territories with different functional profiles. **Who can use this feature?** * Align Operations Users - Browser * [Designating a Primary Territory](#Designat) * Users require an Align License ### Configuring Primary Territory for [![Closed](../../../../Skins/Default/Stylesheets/Images/transparent.gif)Align Operations Users](#) To configure this feature: 1. Ensure [Managing Users in Align](UserMgmt.htm) is configured. 2. Navigate to **Admin > Users & Groups > Permission Sets**. 3. Select the appropriate permission set. 4. Select the **Objects** tab. 5. Grant the following permissions: | Object | Object Permissions | Object Types | Fields | Field Permissions | | --- | --- | --- | --- | --- | | align\_settings\_\_v | CRED | All | primary\_assignment\_handling\_\_v | Edit | | aln\_roster\_member\_territory\_\_v | CRED | All | primary\_\_v | Edit | | aln\_roster\_member\_territory\_model\_\_v | CRED | All | primary\_\_v | Edit | | aln\_roster\_member\_territory\_\_v | CRED | All | override\_primary\_validation\_\_v | Edit | | aln\_roster\_member\_territory\_model\_\_v | CRED | All | override\_primary\_validation\_\_v | Edit | 6. Add the **primary\_\_v** field to the following object page layouts: * roster\_member\_\_v\_territory\_\_v * model\_aln\_roster\_member\_territory\_\_v 7. Add the **primary\_\_v** field to the Roster Member Territory related list on the following object page layouts: * aln\_roster\_member\_\_v * aln\_territory\_\_v * model\_aln\_territory\_\_v 8. Add the **primary\_assignment\_handling\_\_v** field to the align\_setting\_\_v object page layout. 9. Select one or both of the following values for the **primary\_assignment\_handling\_\_v** Align Global Setting: * validate\_roster\_members\_\_v – Prevents users from assigning more than one primary territory to a roster member * validate\_territories\_\_v – Prevents users from assigning more than one primary roster members to the same territory Existing roster member assignments are not retroactively validated when enabling this setting. This setting can only be used in the Global Settings record and cannot be used in field-force specific settings, since end users can be assigned to multiple territories in different Field Forces. [![Closed](../../../../Skins/Default/Stylesheets/Images/transparent.gif)End Users](#) To configure this feature: 1. Ensure [Managing Users in Align](UserMgmt.htm) is configured. 2. Navigate to **Admin > Users & Groups > Permission Sets**. 3. Select the appropriate permission set. 4. Select the **Objects** tab. 5. Grant the following permissions: | Object | Object Permission | Object Types | Fields | Field Permissions | | --- | --- | --- | --- | --- | | align\_settings\_\_v | R | All | primary\_assignment\_handling\_\_v | Edit | | aln\_roster\_member\_territory\_\_v | RE | All | primary\_\_v | Edit | | aln\_roster\_member\_territory\_model\_\_v | RE | All | primary\_\_v | Edit | ### Designating a Primary Territory as [![Closed](../../../../Skins/Default/Stylesheets/Images/transparent.gif)Align Operations Users](#) To designate a territory as being the primary territory of a roster member, select Yes for the primary\_\_v field for the appropriate aln\_roster\_member\_territory\_\_v or model\_aln\_roster\_member\_territory\_\_v records. When the user attempts to create or save a roster\_member\_\_v\_territory\_\_v or model\_aln\_roster\_member\_territory\_\_v record designated as a primary territory, the following validation occurs based on the selected values for the primary\_assignment\_handling\_\_v Align Global Setting: * If validate\_roster\_members\_\_v is selected, all other aln\_roster\_member\_territory\_\_v or model\_aln\_roster\_member\_territory\_\_v records associated with the **roster member** are checked. If any other record is already designated as being a primary territory within the same date range, the user is prevented from saving the record. ![](../../../Resources/Images/Align/UserMgmt/PrimaryTerr1.png) * If validate\_territories\_\_v is selected, all other aln\_roster\_member\_territory\_\_v or model\_aln\_roster\_member\_territory\_\_v records associated with the **territory** are checked. If any other record is already designated as another roster member’s primary territory, the user is prevented from saving the record. ![](../../../Resources/Images/Align/UserMgmt/PrimaryTerr.png) * If both validate\_roster\_members\_\_v and validate\_territories\_\_v are selected, both steps of validation occur Validation in model records does not apply across models, only within the same model. For example, a roster member can be primarily assigned two different territories for the same date range in different projects. Admins can override the validation specified in the primary\_assignment\_handling\_\_v Align Global Setting by selecting Yes for the override\_primary\_validation\_\_v field on the appropriate aln\_roster\_member\_territory\_\_v or model\_aln\_roster\_member\_territory\_\_v records. This field can only be populated via data loading and automatically resets to No as part of the dataload process to prevent future changes that override validation from occuring in the user interface. #### Resolving Multiple Profiles with Primary Territories If a user is assigned to multiple territories, with one territory designated as a primary territory, an integration conflict may occur if the different territories attempt to assign different types of the following records to the user: * Security Profiles * Application Profiles * Layout Profiles * Security Policies This is because users can only be assigned one of each type of these records. If this occurs, a message displays in the header of the corresponding aln\_roster\_member\_\_v record informing the admin that the user’s primary assignment is being used to resolve the conflict when setting these values in CRM. See [Roster Members with Multiple Inherited Functional Profiles](FunctProfiles.htm#Roster) for more information about users with multiple functional profiles. #### Primary Territories and Roster Member Transfers When territories are transferred between roster members, the end\_date\_\_v field of the old aln\_roster\_member\_territory\_\_v record automatically populates with one second prior to the selected transfer date. This ensures aln\_roster\_member\_territory\_\_v representing primary territory assignments do not overlap after a transfer. Additionally, the new assignment is also designated as the primary territory. For example, if the Align admin selected April 1st as the transfer date of a territory, the end\_date\_\_v field of the corresponding aln\_roster\_member\_territory\_\_v record populates as March 31st at 11:59:59 PM. ![](../../../Resources/Images/Align/UserMgmt/PrimaryTerr3.png) ### Related Topics [Managing Users in Align](UserMgmt.htm) [Managing Groups with Functional Profiles](CRMGroups.htm) [Assigning Roster Members in Align](../TerrAssignment/RosterMemberAssignment/RosterMember.htm)