To configure this feature:

1. Ensure the following features are configured:

   • Configuring Align
   • Engage Group Management
   • Configuring Engage Connect Groups
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 Permission
   aln_roster_member__v	CRE	All	engage_group_request__v engage_group_provisioning_status__v engage_group__v engage_connect_group_request__v engage_connect_group_status__v engage_connect_group__v	Edit
   user__sys	CRE	All	engage_group_request__v engage_group_provisioning_status__v engage_group__v	Edit

6. Navigate to Align Admin > Align Settings (Production).
7. Select the Global Align Setting record.

8. Add the following values to the Manage CRM Features multiselect picklist:

   • engage__v
   • engage_connect__v – Only required when using Engage Connect
9. Select Save.

Activating and Managing Field Mappings

1. Navigate to Align Admin > Integrations.
2. Select the Gear icon next to the Vault CRM instance in the Vault CRM section.
3. Select View Field Map.
4. Select CRM Objects to navigate to the inbound mappings.
5. Expand the Roster Member Fields section.
6. Select Describe & Edit.

7. Activate the following system field mappings:

   • engage_group__v
   • engage_group_provisioning_status__v
   • engage_connect_group__v
   • engage_connect_group_status__v

8. Map the following custom field mappings:

   • engage_group_request__v – Map to the engage_group_request__v field in CRM
   • engage_connect_group_request__v – Map to the engage_connect_group_request__v field in CRM
9. Select Save.
10. Select Align Objects to navigate to the outbound mappings.
11. Expand the Roster Member Fields section.
12. Select Describe & Edit.

13. Activate the following system field mappings:

    • engage_group_request__v
    • engage_connect_group_request__v
    • engage_group_provisioning_status__v
    • engage_connect_group_status__v
14. Select Save.

Membership to both Engage and Engage Connect groups is managed via request fields:

1. Navigate to the appropriate aln_roster_member__v record.

2. Populate the appropriate fields:

   • engage_group_request__v – Populate with the name of the Engage group the user should be added to
   • engage_connect_group_request__v – Populate with the name of the Engage Connect group the user should be added to. This field is only required when using Engage Connect.

3. Select Retry Request for the following fields. This step is only necessary when updating existing roster members and ensures the assignment is sent to Vault CRM during the next push:

   • engage_group_provisioning_status__v
   • engage_connect_group_status__v – Only required when using Engage Connect
4. Select Save.

If an import from Vault CRM occurs after Engage license updates are made to existing roster members in Align, those updates will be overwritten by the values from CRM. Therefore, it is recommended to push these updates to Vault CRM before running an import. If a new roster member is created, Engage license updates are not overwritten, since the record does not yet exist in Vault CRM.

The assignment request is processed during the next push to Vault CRM. After the push, the engage_group_provisioning_status__v and engage_connect_group_status__v picklists update to indicate if the assignment request was successful:

• Request Sent – The request has not yet been processed by the Engage server
• No Licenses Remaining – The request failed due to a lack of available licenses. This value only applies to the engage_group_provisioning_status__v picklist.
• Invalid Group Name – The entered group name did not match a group name on the Engage server
• User not in Connect – The requested user is not configured to use Engage Connect. This value only applies to the engage_connect_group_status__v picklist.
• User Create Failed – The requested Engage Connect user could not be created. This value only applies to the engage_connect_group_status__v picklist.
• User Update Failed – The requested Engage Connect user could not be updated. This value only applies to the engage_connect_group_status__v picklist.
• Request Failed – The requested assignment failed
• Success – The requested assignment succeeded

If the assignment in Vault CRM is successful, the engage_group__v and engage_connect_group__v fields update with the name of the Engage or Engage Connect group the user was assigned to. If the assignment in Vault CRM is not successful, review the Align error logs to view more details about the record that failed and the associated user.

• If any fields are missing or incorrect, update them, then reset the appropriate status field to Retry Request, which resends the roster member during the next push to Vault CRM
• If the issue remains unresolved, contact support for further assistance

Admins can remove users from Engage and Engage Connect groups via Align:

1. Navigate to the appropriate aln_roster_member__v record.

2. Populate the appropriate fields:

   • engage_group_request__v – Edit this field to be empty
   • engage_connect_group_request__v – Edit this field to be empty. This field is only required when using Engage Connect.

3. Select Retry Request for the following fields. This step is only necessary when updating existing roster members and ensures the assignment is sent to Vault CRM during the next push:

   • engage_group_provisioning_status__v
   • engage_connect_group_status__v – Only required when using Engage Connect
4. Select Save.

Automatically Removing Users from Engage and Engage Connect Groups

If a roster member is either manually inactivated in Align by updating the crm_user_status__v field to inactive__v, or if the roster member record is inactivated due to the record being end-dated, they are automatically removed from their Engage and Engage Connect groups during the next push to CRM.