<aside> 💡

For information on the Workday integrations, please check out Workday

</aside>

Data migration from Workday uses several Workday APIs, each of which requires varying user  and permission configuration. The setup requires 3 steps:

  1. Configuring Ashby's Integration System User (ISU)
  2. Configuring domain and business process security for Ashby's ISU
  3. Creating the "API Client for Integrations" for Ashby

In each step, we will advise you to copy down some important information that will need to be  configured within Ashby, in order to connect your Ashby and Workday instances, like this:

<aside> 💡

Here is an example of a callout advising you to note important information

</aside>

Configuring Ashby's ISU

  1. Log in to your Workday application using an Administrator account.
  2. In the application's search box, search for 'create user' and then select Create Integration System User.
  3. Enter a User Name and Password.

<aside> 💡

Copy down the username and password for future configuration within Ashby

</aside>

Leave the Require New Password at Next Sign In checkbox unchecked (this user will be accessing Workday programmatically).

  1. Leave the Session Timeout Minutes with its default value of 0, which will prevent the user's sessions from timing out prematurely.
  2. Select the option Do Not Allow UI Sessions (this prevents the account from logging into Workday).

<aside> 💡

If possible, make sure the password does not expire. Otherwise, Ashby's sync will stop when the password expires. You can do this by going to the Maintain Password Rules task and adding Ashby's ISU to the System Users exempt from password expiration field.

</aside>