Concept: Integrations - Employee Provisioning

Workday Peakon Employee voice (WPEV) supports integrations with external account provisioning applications and services using the Simple Cloud Identity Management (SCIM) format.

The Employee Provisioning integration enables Administrators to add and to remove hired and terminated workers from applications and services. Examples: Azure Active Directory and Personio.

Employee provisioning systems don't sync attributes that you restrict on employee records. However, it's possible to sync attributes that you restrict in dashboard for segment scores.

Peakon notifies administrators when the sync of a standard integration has completed or disconnected.

BambooHR

WPEV enables you to create an integration to sync worker data from BambooHR to WPEV.

WPEV extracts employee data from BambooHR and maps it over to compatible fields on WPEV.

WPEV suggests applying the same BambooHR naming convention to your employee fields on WPEV.

Best Practices for BambooHR Integration

For any additional fields on WPEV, ensure that the field name on BambooHR matches the field name on WPEV, excluding the standard fields

Timezone

and

Language

. These fields set automatically through detection. You can also override the fields using manual imports.

To create the token, ensure that it comes from a Full Admin account on BambooHR, because the integration inherits permissions from the issuing account. WPEV synchronizes changes in BambooHR every hour. A full synchronization only occurs on initial setup.

In case of errors or configuration changes, you can start a full synchronization using

Synchronize now

on the integration settings tab. Full synchronization can take up to 30 minutes to complete.

When you add employee records to BambooHR with a future hire date, WPEV also creates the record. Employees don't receive surveys until their hire date.

When you create an employee leaving or exit date on BambooHR, WPEV creates the employee

Separation date

and

Separation reason

fields in WPEV. When the separation date passes, the employees no longer receive surveys. WPEV treats the

Separation date

and

Separation reason

as standard attributes on BambooHR, meaning you don't need to create custom fields on BambooHR for these 2 fields.

Restricted Attributes on WPEV for BambooHR Integration

When Employee attributes access is restricted on WPEV, the attribute won't sync with BambooHR. If your attributes don't sync properly, remove the restriction making the attribute visible on employee records.

Bob

To set up the Bob integration, create an API token on Bob. Ensure it has sufficient permissions enabled to read all employee data. Note that the API token permissions inherit the permissions of the issuing user.

Select

Synchronize now

every time you'd like to sync Bob with WPEV. Alternatively, you can set up automatic synchronization using a webhook from Bob. Enter the webhook in the

Webhook secret

box under the

Real-time updates

section of the

Settings

page.

Any custom fields on Bob will sync to WPEV where the attribute name on WPEV matches the field name on Bob. WPEV doesn't support custom tables from Bob.

When you remove an employee from Bob, WPEV also removes the record.

When you create an employee leaving or exit date on Bob, WPEV creates the employee

Separation date

and

Separation reason

fields in WPEV. Once the separation date passes, the employee no longer receives any surveys.

Personio

WPEV suggests that you apply the same Personio naming convention to your fields on WPEV. Matching field names ensures that field values on Personio map correctly to the corresponding WPEV fields.

Custom Personio fields sync to WPEV when the attribute name on WPEV matches the field name on Personio and with compatible data types.

WPEV synchronizes changes in Personio daily. For errors or configuration changes, you can start a full synchronization using

Synchronize now

on the integration

Settings

Sapling

When users in Sapling match to a user in WPEV based on email addresses, Sapling stores their unique WPEV ID.

Sapling creates a Performance menu for each WPEV ID on user profile pages. When you access the menu, Sapling directs users to their WPEV profile.

Clicking the menu opens a new tab and navigates users to their Peakon profile. Users receive prompts to sign into Peakon first if not already signed in. Sapling users can have multiple performance management integrations enabled. Sapling displays a Performance menu from which to select the app you want to open for the user.