SkyPrep's HRIS integrations allow you to map user data from your HRIS platform to SkyPrep user fields, Custom Labels, Groups, and other supported user properties. Import Rules let you decide which users should be imported into SkyPrep and which users should be skipped.
This article explains the SkyPrep-side Data Mapping and Import Rules used by HRIS and user-import integrations. Your HRIS provider may have different connection steps and available fields, but the SkyPrep-side mapping and rule concepts are similar across supported HRIS integrations.
Who this article is for
This article is for SkyPrep administrators, HRIS administrators, and technical teams who need to decide which users should be imported into SkyPrep and which HRIS fields should update SkyPrep user profiles.
A SkyPrep admin can use this article to understand what choices need to be made. An HRIS or technical admin can use it to confirm which source-system fields are available, populated, and appropriate to send to SkyPrep.
Responsibilities
SkyPrep is responsible for:
Providing the Data Mapping, Import Rules, Users, and Settings tabs.
Reading user data from the connected HRIS once the connection is authorized.
Applying your saved Data Mapping and Import Rules.
Creating, updating, disabling, reactivating, and grouping users according to your SkyPrep settings.
Showing mapped user data and raw payloads where supported.
Troubleshooting SkyPrep-side import errors.
Your team or HRIS provider is responsible for:
Creating and maintaining the HRIS connection, service account, API key, OAuth authorization, or file export.
Granting the required HRIS permissions.
Confirming that required fields exist and are populated.
Confirming that HRIS data is accurate before SkyPrep imports it.
Troubleshooting provider-side permissions, missing fields, API limits, outages, or source-data issues.
Data Mapping
To begin, navigate to your HRIS integration page in SkyPrep and click the Data Mapping tab.
Data Mapping tells SkyPrep which HRIS field should update each SkyPrep user field.
The SkyPrep Property column lists the available SkyPrep user fields. For each SkyPrep field, choose the HRIS field that should be used as the Primary Value.
If the Primary Value is blank for a user in the HRIS, SkyPrep will use the Secondary Value if one is configured.
First Name, Last Name, and Email/Username are required for user creation and updates. Email/Username must be unique in SkyPrep.
Mapped fields can update standard SkyPrep user fields, Custom Labels, email notification settings, SkyPrep Groups, termination fields, and manager/hierarchy fields when supported by the integration.
Custom HRIS fields
Some HRIS fields may not appear as preset dropdown options in the Data Mapping tab. If a field is available in the HRIS payload but is not listed as a selectable mapping option, SkyPrep can add it as a custom mapping field.
SkyPrep provides a one-time complimentary setup for custom HRIS mapping fields.
Before contacting SkyPrep, review the HRIS payload and make a list of all custom fields you want to add. For each field, please provide:
The field name you want to map.
Where the field appears in the payload.
Any rules needed to identify the correct value.
An example user where the field is populated.
For example, some HRIS systems include multiple job records for a user. If you only want the current job title, tell SkyPrep which part of the payload identifies the current job, such as a primary indicator, active status, or effective date.
Once you have the full list of custom fields, contact your Customer Success Manager or create a ticket through the SkyPrep bot. SkyPrep will review the payload and set up the custom mapping fields for you.
Import Rules
After setting up your Data Mapping, click the Import Rules tab. This is where you define which users are imported or skipped.
Click Add Rule to begin.
Rules can be configured to:
Import the User
Skip Importing the User
If a user matches a Skip Importing the User rule, SkyPrep will not create that user and will not update that user’s data from the integration.
If needed, you can stack multiple rules to tailor the import behavior to your organization’s requirements.
Before enabling automatic imports, confirm:
Your rules include the correct users.
Required fields are mapped.
Skipped users are intentionally excluded.
Terminated or inactive users are handled according to your Settings tab.
Group mappings will not remove users from groups unexpectedly.
How mappings and rules affect Settings
Data Mapping and Import Rules work together with the integration Settings tab.
Auto Import New Users creates new SkyPrep users when they appear in the HRIS, match Import Rules, and have the required mapped fields.
Termination Date Action uses mapped termination data to decide whether login should be disabled.
Remove users from groups they are no longer part of in the HRIS uses mapped group data to remove users from SkyPrep Groups when the HRIS value changes.
Deactivate users in the LMS that are no longer in the HRIS disables users who were previously imported but no longer appear in the HRIS data.
Reactivate terminated users reactivates users when they are no longer marked as terminated in the HRIS.
Deactivate existing users who do not match import rules disables users when they no longer match your saved Import Rules.
Update profiles of existing deactivated users allows mapped fields to continue updating for disabled SkyPrep users.
Reviewing users before import
Use the Users tab to preview mapped HRIS users before running an import. Where supported, use View Payload to inspect the raw HRIS data SkyPrep received for a user.
If a value does not appear as expected:
Confirm the field is populated in the HRIS.
Confirm the integration account has permission to read that field.
Check the raw payload.
Update the Data Mapping if the wrong HRIS field is selected.
Refresh the Users tab after changing mappings or source data.
When to contact support
Contact SkyPrep Support when:
SkyPrep is not applying a saved mapping or rule as expected.
A SkyPrep import produces an unexpected error.
The Users tab shows data, but the import result is not correct.
Contact your HRIS or technical team when:
A field is missing from the HRIS data.
A user is missing from the HRIS export or API response.
The integration account lacks permission to read user data.
HRIS data is inaccurate or incomplete.