This article is intended for HelloTeam users with ADMIN Access Level

Before linking your Workday, we'll need to make sure that the correct permissions are enabled. Below are some detailed steps for granting permissions. Steps One through Five are done within your Workday portal, whereas the last step is done with your HelloTeam respresentative.

Step One: Create an Integration System User (ISU)

In your Workday portal, log into the Workday tenant.
In the Search field, type Create Integration System User.
Select the Create Integration System User task.
On the Create Integration System User page, in the Account Information section, enter a user name, and enter and confirm a password.
Click OK.

Note: due to xml encoding, "&", "<", and ">" cannot be included in the password.

Note: Ensure Require New Password at Next Sign In is NOT checked.

Note: You'll want to add this user to the list of System Users to make sure the password doesn't expire.

Step Two: Create a Security Group and Assign an Integration System User

Now, add this Integration System User to a Security Group:

In the Search field, type Create Security Group.
Select the Create Security Group task.
Click OK.
On the Create Security Group page, from the Type of Tenanted Security Group pull-down menu, select Integration System Security Group (Unconstrained).
In the Name field, enter a name.
Click OK.
On the Edit Integration System Security Group (Unconstrained) page, in the Name field, enter the same name you entered when creating the ISU in the first section.
Click OK.

Step Three: Configure Domain Security Policy Permissions

In the Search field, type Maintain Permissions for Security Group
Make sure the Operation is Maintain, and the Source Security Group is the same as the security group that was assigned in Step 2.
Add the corresponding Domain Security Policy with GET operation:

Please note the permissions listed below are the required permissions for the full HRIS API. Permissions can differ from implementation to implementation.

Parent Domains for HRIS:

Job Requisition Data
Person Data: Name
Person Data: Personal Data
Person Data: Home Contact Information
Person Data: Work Contact Information
Worker Data: Compensation
Worker Data: Workers
Worker Data: All Positions
Worker Data: Current Staffing Information
Worker Data: Public Worker Reports
Worker Data: Employment Data
Worker Data: Organization Information
Reports: Pay Calcuation Results for Worker (Results)
Worker Data: Time Off**

** Specific instructions to allow access to Time Off data can be found here.

Parent Domains for ATS:

Candidate Data: Job Application
Candidate Data: Personal Information
Candidate Data: Other Information
Pre-Hire Process Data: Name and Contact Information
Job Requisition Data
Person Data: Personal Data
Person Data: Home Contact Information
Person Data: Work Contact Information
Manage: Location
Worker Data: Public Worker Reports

For a more detailed breakdown of the functional areas that are needed: here

Step Four: Activate Security Policy Changes

In the search bar, type "Activate Pending Security Policy Changes" to view a summary of the changes in the security policy that needs to be approved.
Add any relevant comments on the window that pops up
Confirm the changes in order to accept the changes that are being made.

Step Five: Validate Authentication Policy is Sufficient

Check the Manage Authentication Policies section to ensure the ISU you created is added to a policy that can access the necessary domains. It should not be restricted to only the "SAML" Allowed Authentication Types – if this is the case, you can create a new Authentication Policy with a "User Name Password" Allowed Authentication Type.

Editing Authentication Policies
Create an Authentication Rule, and add the Security Group to the Rule
Make sure the Allowed Authentication Types is set to specific User Name Password or set to Any

Step Six: Activate All Pending Authentication Policy Changes

In the search bar type, Activate All Pending Authentication Policy Changes
Proceed to the next screen, and confirm the changes. This will save the Authentication Policy that was just created.

Step Seven: Obtain the Web Services Endpoint for Workday Tenant

We'll need access to your specific Workday web services endpoint:

Search in Workday for Public Web Services.
Open Public Web Services Report.
Hover over Human resources and click the three dots to access the menu.
1. If you are integrating with your Workday ATS, please find Recruiting instead and access that menu.
Click Web Services > View WSDL.
Navigate to the bottom of the page that opens and you'll find the host.
Copy everything until you see /service. This should look something like https://wd5-services1.myworkday.com/ccx.

Be sure to share your credentials with your HelloTeam representative so that they can complete your authentication.

Workday URL: The Web Services Endpoint you found from Step 5 into Merge Link.
User ID: The Integration System User name for the user created in Step One.
Password: The Integration System User password for the user created in Step One.
Workday Tenant Name: Workday Tenant name.
1. Example: If you sign in at "https://wd5-services1.workday.com/acme", share "acme".

Notes

Linked Implementation Workday accounts will result in slower syncs as there are fewer resources dedicated to the tenant.
The password used cannot contain an "&" or "<", ">" signs.
Please make sure to exempt the ISU Account from MFA and SSO

To ensure you are viewing the most current information
regarding this specific HRIS, please visit:

https://help.merge.dev/en/articles/5699428-workday-isu-and-web-services-endpoint-authentication