Source: https://vaultcrmhelp.veeva.com/doc/Content/CRM_topics/Align/UserMgmt/UserMgmt.htm

## 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?**

* Align Operational Users – Browser
* [Managing Users](#Managing)
* Users require an Align License

### Configuring User Management for

[![Closed](../../../../Skins/Default/Stylesheets/Images/transparent.gif)Align Operational Users](#)

To configure this feature:

1. Ensure [Configuring Align](../Configuration/ConfiguringAlign.htm) is complete.
2. Navigate to **Admin > Users & Groups > Permission Sets**.
3. Select the appropriate Permission Set.
4. Select **Objects**.
5. Grant the following permissions:

   | Object | Object Permission | Object Types | Fields | Field Permission |
   | --- | --- | --- | --- | --- |
   | crm\_security\_profile\_\_v | R | All | All | Read |
6. Navigate to **Align > Align Admin > Align Settings (Production)**.
7. Select **Enabled** for the Manage CRM Users picklist.
8. 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:

1. Navigate to the **Align Integrations** page in the Integrations tab.
2. Select **View Field Map** in the Gear menu for the appropriate Vault CRM instance.
3. Select the **Align Objects** tab.
4. 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

[![Closed](../../../../Skins/Default/Stylesheets/Images/transparent.gif)Align Operational Users](#)

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:

1. Navigate to the appropriate **aln\_roster\_member\_\_v** record.
2. Navigate to the **CRM User Management** section.
3. Update the Mastered by Align picklist to **Yes**.
4. 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](FunctProfiles.htm), but can be manually overridden:

1. Navigate to the appropriate **aln\_roster\_member\_\_v** record.
2. Navigate to the **CRM User Management** section.
3. Use the **crm\_security\_profile\_\_v** lookup field to select the appropriate crm\_security\_profile\_\_v record.

### Related Topics

[Using Functional Profiles](FunctProfiles.htm)

[Managing Layout Profiles in Align](LayoutProfiles.htm)

[Managing Groups with Functional Profiles](CRMGroups.htm)