Overview

Identity configuration is how Moveworks builds a complete user profile for every person. The end goal is to fill the Moveworks user data dictionary for each ingested user.

This happens in three main steps:

1. Add connectors
   Connect the external systems that contain user data, such as your HR system, identity provider, or directory.
2. Map data for each connector
   For every connected system, choose which external attributes should map to which fields in the Moveworks user data dictionary.
3. Set override rules
   By default, Moveworks takes all attributes from the primary system. If you want certain fields to come from secondary systems instead, you configure that here. This is where you decide, for each field in the final user profile, which system should provide the value, whether values should be combined from multiple systems, and what format the final value should use.

Steps to configure Identity module

Step 1 : Add connectors 

Please ensure that you validate your connector before moving to the next step to prevent scenarios of user ingestion failure.

Step 2 : Configure source mapping

This is where you map user attributes from each connector to Moveworks’ user object. 

For each system there are some pre-mapped attributes that MW provides out of the box. You can see them under “View attributes”

On this screen : 

• You can map additional user attributes 
• You can add filter users per source & add processors. 
• You can see a set of sample users and their attributes.

How to map an additional attribute ?

1. Expand attributes of a source and then click”+ADD

Select a MW’s user field which you want your attribute to be mapped to.

Then, use the MW DSL builder to configure the mapping rule.

You can leverage the autocomplete to select external attribute that you want to use for mapping.

Once you have configured your DSL rule, you can test this live for a user and see what the output is. If it is your desired output, you can SAVE the mapping. 

How to add filters and processors ? 

You can add them by click on the filter icon. 

Filters are added to restrict MW from ingesting all users and their attributes. 

Processors are added to compute and auto populate value of a few attributes based on the mapped attributes. 

Example : Geocode processors take in “country_code” attribute , computes the user geocode and populates to their final user profile.

Step 3 : Configure override mapping

By default MW ingests all mapped attributes from your primary system. 

Use override mapping when : 

1. You want an attribute to be pulled from any secondary system.
2. You want an attribute to be derived from multiple systems (primary OR secondary)

Step 4 : Configure JOIN KEY

Join key is very important for user ingestion. 

It is by using the JOIN key, MW joins attributes coming from multiple systems and constructs a final user profile.

This join key is usually an attribute whose value does not change across systems.
You can also write a DSL rule to derive a value from multiple attributes. 

Step 5 : Validate final user profile & Submit

This is where you can dry run your identity configuration. 

This section tells you whether for the given user email, if the system was able to build a final user profile across multiple systems. 

Common scenarios : 

1. Failed to process user record : This means that for the give user email, no profile was found for that system. You can try with a different user.
2. Join key mismatch : This means that for the given email, the value of the joining key does not match across systems. In such scenarios attributes that are leveraging secondary systems would become null, and only the attributes coming from primary systems would be populated for this user.

This section gives you the final profile of the user whose email you provided. 
Use it to validate the attributes and rectify if something does not look right. 

FAQs

1. How to create custom attribute in the new journey ? Go to attribute registry > Add your attribute > The custom attribute shows up in source mapping drop down

2. How to add user tags ?
   
   1. Click on ‘ADD’ under source mapper

   
   2. Select user tags from the drop down

3. Write your DSL and test it