Mapping sets correlate user/group identity attributes between HelloID and external entities. Specifically, HelloID uses mapping sets for:
- Synchronizing the user directory from Active Directory or other supported identity providers (data is mapped into HelloID)
- Single sign-on application authentication via SAML, OIDC, etc. (data is mapped out of HelloID)
For example, mapping sets specify which attributes from an IdP's user schema are mapped onto which attributes in the HelloID user schema, such as username and email. Similarly, mapping sets specify which HelloID user attributes are passed to single sign-on applications when a user signs into them.
Mapping sets are not created manually. Rather, a mapping set is created automatically by HelloID whenever you add a new application, identity provider, or Active Directory configuration. The mapping set is then displayed in the mapping sets overview grid and can be edited.
Note that mapping sets are only relevant when you're using a HelloID-supported IdP that comes with a directory sync task. If you're using a custom directory (i.e., syncing users from an unsupported system, using the HelloID API via a custom task), you will not have a mapping set. Instead, you will simply write your mapping logic inside your custom sync script.
Mapping Sets Overview
To view mapping sets within your organization's HelloID environment, go to Directory > Mapping sets.
The following information is listed for Mapping sets:
The mapping set's name, as displayed throughout the HelloID admin dashboard. Names cannot be changed. Each mapping set is permanently named according to the identity provider or application to which it corresponds.
Select the Edit link to modify a mapping set.
Next: Edit a mapping set >>