Setup Considerations: Employee Sync Integrations

You can use this topic to help make decisions when planning your configuration and use of employee sync integrations. It explains:

Why to set it up.

How it fits into the rest of Workday.

Downstream impacts and cross-product interactions.

Security requirements and business process configurations.

Questions and limitations to consider before implementation.

Refer to detailed task instructions for full configuration details.

What It Is

Employee sync integrations enable you to automatically transfer employee data and reporting lines from your third-party Human Resources Information System (HRIS) or identity provider to Workday Peakon Employee Voice.

Business Benefits

Minimize admin effort with automated employee import and management.

Ensure that employee records and demographic data remain accurate and up to date for precise segmentation and reporting.

Use Cases

Automate the provisioning and de-provisioning of users using SCIM 2.0 integrations with identity providers like Okta or Azure Active Directory.

Sync employee demographic data directly from third-party HR systems, such as BambooHR, HiBob, or Personio, to automatically create and update segments in Peakon.

Questions to Consider

Questions	Considerations
How do you plan to import employee data?	You can upload your employees manually using an Excel file, or you can sync your employees automatically using a Human Resources system integration. To sync employees automatically, you must set up an integration using SCIM 2.0 supported systems or out-of-the-box integrations like BambooHR, HiBob, or Personio.
Do all employees have at least 1 unique identifier?	Each employee must have a unique account email address and/or a unique employee number to use automatic syncs. Account email addresses cannot be reused across employees.
How do you want to manage leavers?	You can manually import employee separation dates, or let an automatic employee sync update this information automatically. To stop employees from receiving surveys from their separation date onward automatically, configure your integration to update separation dates from your HR system.

Recommendations

Change attribute and segment names in Peakon before doing a sync to prevent the creation of new segments if there's no exact match, or errors if there are no matching attribute names.

Use the

Sync Information

tab on employee records to troubleshoot issues when updating employees using an integration.

Requirements

Configure your attributes structure in Peakon before initiating an employee sync.

Map your attributes to standard values if you're automatically syncing your employees from a different system.

Ensure each employee has a unique identifier, such as an email address or employee number, in your HR system.

Limitations

It is not possible to have an integration with 2 Human Resources systems at the same time. It is not possible to backdate segment values through an automatic sync.

You can backdate values only through an Excel upload or a manual update on the employee record.

Tenant Setup

No impact.

Security

Only administrators can create the integration between your Human Resources system and Peakon. Users require the View employees
and Update employees
permissions to access and update employee records populated by the integration.

Business Processes

No impact.

Reporting

No impact.

Integrations

Integrations or Web Services	Considerations
SCIM 2.0	Connect Peakon to your people management tool to automatically provision users into Peakon. You can use SCIM 2.0 to set up integrations with Sapling, Okta, and Azure Active Directory.
Third-party HRIS integrations	You can populate employee data and their segments by integrating Peakon with out-of-the-box integrations for BambooHR, HiBob, and Personio.

Connections and Touchpoints

Workday offers a Touchpoints Kit with resources to help you understand configuration relationships in your tenant. Learn more about the Workday Touchpoints Kit on Workday Community.