Source: https://vaultcrmhelp.veeva.com/doc/Content/CRM_topics/Align/Configuration/ConfiguringAlign.htm ## Configuring Align Before using the Align module, you should understand the components, and then configure the functionality for all users. [![Closed](../../../../Skins/Default/Stylesheets/Images/transparent.gif)Components](#) #### Align Territory (aln\_territory\_\_v) Align territories function similarly to the Vault CRM territory\_\_v object used in Territory Management. However, Align Territories represent past, present and future assignments, enabling Align operational users to prepare assignments before they push them to Vault CRM. #### Align Account Territory Assignments (aln\_account\_territory\_\_v) Align account territory assignments associate accounts with Align territories. These assignments are frequently automated using Account Assignment Rules, and assignments are both start and end dated to denote when the account was assigned to the territory. #### Field Forces (aln\_\_field\_force\_\_v) Field forces are a collection of Align territories that have a common focus. For example, a field force could contain all cardiology medical users or all oncology medical users. #### Roster Member (aln\_roster\_member\_\_v) Roster members are the representation of user\_\_sys records within the context of Align. Roster members are assigned to territories via start and end dated assignment records. Additionally, admins can designate certain roster members as being mastered by Align, meaning all changes to the corresponding user\_\_sys record are overridden when the next push to Vault CRM occurs. ### Configuring Align for [![Closed](../../../../Skins/Default/Stylesheets/Images/transparent.gif)Align Operational Users](#) To configure this module: 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 Permission | Object Types | Fields | Field Permission | | --- | --- | --- | --- | --- | | account\_\_v | R | All appropriate object types | All Fields | Read | | address\_\_v | R | All appropriate object types | All Fields | Read | | align\_settings\_\_v | CRED | n/a | All Fields | Edit | | aln\_account\_exclusion\_\_v | CRE | All | All Fields | Edit | | aln\_account\_rule\_\_v | CRE | All | All Fields | Edit | | aln\_account\_rule\_criteria\_\_v | CRED | All | All Fields | Edit | | aln\_account\_territory\_\_v | CRE | All | All Fields | Edit | | aln\_country\_filter\_\_v | CRED | All | All Fields | Edit | | aln\_field\_force\_\_v | CRE | All | All Fields | Edit | | aln\_field\_force\_product\_\_v | CRE | All | All Fields | Edit | | aln\_field\_mapping\_\_v | CRED | All | All Fields | Edit | | aln\_footprint\_\_v | CRE | All | All Fields | Edit | | aln\_footprint\_geography\_\_v | CRE | All | All Fields | Edit | | aln\_functional\_profile\_\_v | CRE | All | All Fields | Edit | | aln\_functional\_profile\_application\_role\_\_v | CRED | All | All Fields | Edit | | aln\_functional\_profile\_field\_force\_\_v | CRED | All | All Fields | Edit | | aln\_functional\_profile\_group\_\_v | CRED | All | All Fields | Edit | | aln\_geography\_\_v | CRED | All | All Fields | Edit | | aln\_geography\_territory\_\_v | CRE | All | All Fields | Edit | | aln\_process\_monitor\_\_v | CRE | All | All Fields | Edit | | aln\_process\_task\_\_v | CRE | All | All Fields | Edit | | aln\_rollup\_rule\_\_v | CRED | All | All Fields | Edit | | aln\_rollup\_rule\_criteria\_\_v | CRED | All | All Fields | Edit | | aln\_roster\_member\_\_v | CRE | All | All Fields | Edit | | aln\_roster\_member\_application\_role\_\_v | CRE | All | All Fields | Edit | | aln\_roster\_member\_territory\_\_v | CRE | All | All Fields | Edit | | aln\_targeting\_rule\_channel\_\_v | CRED | All | All Fields | Edit | | aln\_targeting\_rule\_product\_\_v | CRED | All | All Fields | Edit | | aln\_territory\_\_v | CRE | All | All Fields | Edit | | aln\_territory\_footprint\_\_v | CRE | All | All Fields | Edit | | aln\_territory\_product\_\_v | CRE | All | All Fields | Edit | | aln\_vault\_instance\_\_v | CRE | All | All Fields | Edit | | aln\_veeva\_workday\_org\_\_v | R | All | All Fields | Read | | application\_profile\_\_v | R | All appropriate object types | All Fields | Read | | application\_role\_\_v | R | All appropriate object types | All Fields | Read | | child\_account\_\_v | R | All appropriate object types | All Fields | Read | | currency\_\_sys | R | All appropriate object types | All Fields | Read | | language\_\_sys | R | All appropriate object types | All Fields | Read | | language\_locale\_\_sys | R | All appropriate object types | All Fields | Read | | mc\_cycle\_\_v | CRE | All appropriate object types | All Fields | Edit | | mc\_cycle\_channel\_\_v | CRED | All appropriate object types | All Fields | Edit | | mc\_cycle\_plan\_\_v | CRED | All appropriate object types | All Fields | Edit | | mc\_cycle\_product\_\_v | CRED | All appropriate object types | All Fields | Edit | | product\_\_v | R | All appropriate object types | All Fields | Read | | product\_metrics\_\_v | R | All appropriate object types | All Fields | Read | | security\_policy\_\_sys | R | All appropriate object types | All Fields | Read | | security\_profile\_\_sys | R | All appropriate object types | All Fields | Read | | user\_\_sys | R | All appropriate object types | All Fields | Read | | vcountry\_\_v | R | All appropriate object types | All Fields | Read | 5. Navigate to the Admin tab of the permission set. 6. Grant Read access to **Object Lifecycles**. 7. Navigate to the **Application** tab of the permission set. 8. Select the following check boxes: * Access API * Metadata API 9. Navigate to the **Tabs** tab. 10. Grant access to the **Align** tab collection. 11. Grant access to the following tabs: * aln\_accounts\_\_v * aln\_countries\_\_v * aln\_field\_forces\_\_v * aln\_footprints\_\_v * aln\_functional\_profiles\_\_v * aln\_geographies\_\_v * aln\_home\_\_v * aln\_integrations\_\_v * aln\_products\_\_v * aln\_roster\_members\_\_v * aln\_rules\_\_v * aln\_settings\_production\_\_v * aln\_territories\_\_v 12. Ensure users have visibility to the appropriate account\_\_v records, for example, using [Custom Sharing Rules](https://platform.veevavault.help/en/gr/25494/). #### Defining the Align Integration User The Align Integration User should be used for daily processing jobs in Align. Certain processing jobs need to use a Vault User Account to read and update Vault records. To define the Align Integration User: 1. Navigate to **Align Admin > Integrations**. 2. Select the Gear menu in the in Align section. 3. Select **Edit**. 4. Select the appropriate user. Users selected as the Align Integration User must meet the following requirements: * The user must have English selected as their language * The user must belong to the VaultOwner group 5. Enter the selected user's password. It is recommended that the Align Integration User's password never expire, as resetting the password affects integrations. 6. Select **Save** to validate the entered credentials. ### Related Topics [Integrating Align with Vault CRM](AlignCRMIntegration.htm) [Using Account Assignment Rules in Align](../TerrAssignment/AccountAssignment/AcctAssignmentRule.htm) [Managing Geographies in Align](../TerrAssignment/ManageGeo/Geography.htm)