Managing Users in Align
Align operational users can create and manage Vault CRM users via aln_roster_member__v records within Align, simplifying the alignment process. Align operational users can perform the following tasks via User Management:
- Control which users are mastered by aln_roster_member__v records in Align versus the corresponding user__sys record. Mastering refers to which record is responsible for managing changes made to the user. Changes made to a record on non-mastered systems are overwritten during the next data synchronization.
- Update roster members in Align and push the changes
- Create new roster members in Align and push the record as a new user__sys record, along with all of the proper assignments
Who can use this feature?
- Browser Users
- Users require an Align License
- Align Operational Users
Configuring User Management for

To configure this feature:
- Ensure Configuring Align is complete.
- Navigate to Admin > Users & Groups > Permission Sets.
- Select the appropriate Permission Set.
-
Select Objects.
-
Grant the following permissions:
Object Object Permission Object Types Fields Field Permission crm_security_profile__v R All All Read - Navigate to Align > Align Admin > Align Settings (Production).
-
Select Enabled for the Manage CRM Users picklist.
- Select Save.
User Field Mapping Between CRM and Align
Once User Management is configured, admins can customize the mapping between aln_roster_member__v records and user__sys records:
- Navigate to the Align Integrations page in the Integrations tab.
- Select View Field Map in the Gear menu for the appropriate Vault CRM instance.
- Select the Align Objects tab.
- Navigate to the Roster Member section.
The following table represents the default mappings between aln_roster_member__v records and user__sys records:
aln_roster_member__v |
user__sys |
---|---|
address_line_1__v |
street__v |
alias__v |
alias__sys |
city_cda__v |
city__v |
crm_country_code__v |
country__v |
crm_language__v |
language__sys |
crm_locale__v |
locale__sys |
crm_security_profile__v |
security_profile__sys |
crm_time_zone__v |
timezone__sys |
crm_user_status__v |
status__v |
delegated_approver__v |
delegatedapproverid__v |
email__v |
email__sys |
first_name_cda__v |
first_name__sys |
last_name_cda__v |
last_name__sys |
manager__v |
manager__v |
master_align_id__v |
master_align_id__v |
nickname__v |
communitynickname__v |
state_aln |
state_province__v |
username__v |
username__sys |
The Roster Member Fields section in the CRM Objects tab continues to manage the mapping of fields for CRM-mastered records.
Managing Users as

After enabling User Management, admins can use the CRM User Management section on all aln_roster_member__v record detail pages to indicate how the record is mastered, as well as view information from the corresponding user__sys record.
Designating Roster Members as Align-Mastered
When a roster member is designated as Align-mastered, all changes made to that record on mapped fields must originate from the aln_roster_member__v record.
To master roster members in Align:
- Navigate to the appropriate aln_roster_member__v record.
- Navigate to the CRM User Management section.
- Update the Mastered by Align picklist to Yes.
-
Repeat this process for all appropriate records. Users can also use the Vault Loader to repeat this process in bulk. When using the Vault Loader to master roster members in Align, ensure all aln_roster_member__v records have the following required fields populated:
- alias__v
- crm_country_code__v
- crm_language__v
- crm_locale__v
- crm_security_profile__v
- crm_user_status__v
- crm_time_zone__v
- email__v
- first_name_cda__v
Roster members mastered by Align must have a populated crm_time_zone__v field. This field enables admins to control the timezone of the corresponding user__sys record.
Roster members mastered by Align are skipped during imports. New roster members mastered by Align are pushed as new user__sys records. Existing roster members with a status__v field of active__v update the corresponding user__sys record. Changes made to Align-mastered user__sys records are overwritten during the next push if the change was made on a mapped field.
The crm_imported_security_profile__v field on the aln_roster_member__v object should not be used when the roster member is managed by Align. Removing this field from page layouts is recommended.
Align operational users can control a user__sys record’s status from Align if the corresponding record is Align-mastered using the crm_user_status__v field. This enables users to create inactive user__sys records in Align before their start date and activate the corresponding user__sys record at a later date. This also enables administrators to mark offboarded roster members as inactive.
If a manager or delegated approver is assigned to an Align-mastered roster member, the aln_roster_member__v record representing the manager or approver is also pushed, even if that record is not designated as Align-mastered.
Assigning User Profiles
Vault CRM Security Profiles automatically import when User Management is configured. Imported Security Profiles enhance the roster member creation process by enabling users to assign Security Profiles to Align-mastered roster members.
Security Profiles import as crm_security_profile__v records in Align with the following properties:
- name__v – The name of the corresponding Security Profile
- status__v – active__v
- crm_record_id__v – The ID field of the corresponding Security Profile
crm_security_profile__v records are deleted during an import if they do not have a corresponding Security Profile. This means if a Security Profile is deleted, the corresponding crm_security_profile__v record is deleted during the next import. An error occurs if a crm_security_profile__v record marked for deletion is assigned to a roster member or functional profile record.
Security Profiles are typically assigned via Using Functional Profiles, but can be manually overridden:
- Navigate to the appropriate aln_roster_member__v record.
- Navigate to the CRM User Management section.
- Use the crm_security_profile__v lookup field to select the appropriate crm_security_profile__v record.