After setting up a source, regardless of the sync method you choose, you will need to set up mappings. A mapping is a translation from a property on a person in your data source, to an attribute on a person in Sift. For example, in a CSV source this source property is defined by a header in your CSV file, where in something like an Azure or LDAP source, it would be defined by the properties on people inside of that source.

Note: Any properties from your data source that are not mapped will not be consumed by Sift. We only consume what you elect to give us!

Assigning Your Mappings

Use the text inputs on the left hand side to enter the property names from your source. Depending on source type, some of these properties may be pre-populated, or an autocomplete may be provided for suggestions.

Examples of source properties for:



Note: GSuite Collection Properties

The GSuite API will return some properties like phone numbers and addresses in an array. To support retrieving these types of attribute, you'll need to provide us some additional context about the type of item you're retrieving. Start providing one of these items by typing the name of the collection (e.g. phones) into the left input, and we will ask for some further information.

Example: Mapping a mobile phone number from GSuite

Step 1: Assign required mappings

Sift requires mapping a Primary Key for all sources. Primary Sources also require First Name, Last Name, and Email Address.

For your primary key, we recommend a unique identifier that will never change across the lifetime of your user in your systems. This is usually something like an employee id number. If you want to add secondary data sources in this directory, this same identifier will need to exist in all of them. 

Step 2: Assign additional data mappings

Providing other pieces of data to Sift is optional, but encouraged! Use the Additional Attributes section to provide Sift with other pieces of data that you'd like to include on your profile pages and/or in your search. Use the dropdown menu on the right hand side of the mapping to choose which Sift attribute to map to. If you do not see an attribute here that represents that data you're attempting to map, you may need to create it.

Step 3: Assign the Hierarchy Mapping

In order to use features in Sift like our Org Chart or parts of our profile page, you'll need to assign the hierarchy mapping. The hierarchy mapping is used to build your organization structure by letting us know which attribute defines a person's direct leader (manager). 

On the left side of this mapping, provide which property on a person in your data source represents a reference to their direct manager  (Ex: "managerEmail"). On the right side of this mapping, type which property the above property points to on another person in your data source (Ex: "email")

Where do I go next?

After saving your mappings and setting up your integration, you should be ready to sync your data. You may always come back and adjust mappings as needed.

Did this answer your question?