All Collections
Getting Started
Terminology Guide/Glossary
Terminology Guide/Glossary
Tim Kamen avatar
Written by Tim Kamen
Updated over a week ago

Below is a list of common terms used throughout Sift and a brief description of each one to help with the implementation process.


A user who has access to all features of the admin dashboard and some additional permissions inside of the Sift People Directory to manage profiles.


Describes a common piece of data on your people, such as an office phone number, a collection of skills, or an email address. Attributes can be created and updated by admins, added to profile pages, and/or be imported from your data systems.

Azure Active Directory

One of our three data sync methods. Azure Active Directory (AAD) is Microsoft’s cloud-based identity and access management service.


The second step in getting Sift set up for your organization. Configuration mainly deals with the appearance of your organization’s Sift.

Complementary Source

A Complementary Source provides supplemental pieces of data for users. Not all Directories must include a secondary source. Be sure to include the same primary key on the Complementary Source as you did on the Primary Source.


One of our three data sync methods. You are able to add data into Sift via a spreadsheet saved as a .csv. To automate this process in a secure way, use our easy-to-set-up SFTP integration.

Custom Widget

Allows easy access to Sift from your company intranet through embedded HTML.


Used to represent a segment of your user population coming from your data sources. Most organizations will have one Directory that contains all of their users. However it is possible to have multiple Directories if some of your user data is in a different place.


The first step in getting Sift set up at your organization. During integration you are ensuring that all of your data is sent to Sift properly and appearing on Sift profiles neatly.


One of our three data sync methods. This method will let you sync with on-premises systems such as Active Directory or other LDAP compatible sources.


To ensure your data transfers to Sift correctly, you must create mappings from your data source to Sift’s attributes. An example is mapping “employee_email” to show as “Email” in Sift.


The third step in getting Sift set up at your organization. Onboarding helps to ensure that all employees at your organization are aware of Sift and how it will benefit your organization.


In addition to the Admin access, Owners have some special protections against data deletion and misconfiguration. This is to ensure that you never reach a state where nobody at your company has access to Sift.

Primary Source

Responsible for the provisioning of users (addition and deletion), but can also have additional sources for supplemental pieces of data on those same users. Each Directory will have a Primary Source.

Profile Layout

The order in which Attributes appear on a Sift profile page.

Sift Support

The ability for an admin to assign an email to receive all Sift questions. Also the ability for an employee to contact someone at their own organization to help them with Sift.


The fourth and final step in getting Sift set up at your organization. Sustainment ensures that Sift will be known, loved, and useful to your organization for years to come.


The ability to add colors, logos, and default photos to your organization’s Sift.

Did this answer your question?