Configuring Align
Before using the Align module, you should understand the components, and then configure the functionality for all users.
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 upcoming, rather than current assignments, enabling Align operational users to edit assignments before they publish to the main territory structure. Align Territories are applicable to all lines of business, profit centers, and cost centers; from sales to medical field personnel.
Align Account Territory Assignments (aln_account_territory__v)
Align account territory assignments associate accounts with Align territories. These assignments are frequently managed in bulk 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 from Align occurs.
Configuring Align for
Align Operational Users
To configure this module:
- Navigate to Admin > Users & Groups > Permission Sets.
- Select the appropriate permission set.
- Select the Objects tab.
-
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_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 - Navigate to the Application tab of the permission set.
-
Select the following check boxes:
- Access API
- Metadata API
- Navigate to the Tabs tab.
- Grant access to the Align tab collection.
-
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
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:
- Navigate to Align Admin > Integrations.
- Select the Gear menu in the in Align section.
- Select Edit.
-
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
-
Enter the selected user's password.
It is recommended that the Align Integration User's password never expire, as resetting the password affects integrations.
- Select Save to validate the entered credentials.
