Skip to main content
You connect Dayforce once for each client that uses it, with five values for that client’s Dayforce company: the environment, the API host, the company ID, and a web services user’s name and password.

​
1. Set up a web services user in Dayforce

The client’s Dayforce administrator does these steps, in that client’s Dayforce.
1

Create a role for Neo

In System Admin → Roles, create a role for Neo. On the Features tab, under HCM Anywhere → Web Services, give it Read Data. For Neo to write back an employee’s work email or Dayforce sign-in, also give it the PATCH/POST Employee HR Data subfeature.
2

Give the role field access

On the Web Services Field-Level Access tab, under RESTful Services → Human Resources → Employee, enable XRefCode and the fields your agents read, such as the work assignments, employment statuses, managers, locations and contacts. To write back a Dayforce sign-in, also allow creating SSO logins under Employee Profile → Security Settings on the Authorizations tab.
3

Create the user

Create a Dayforce user for Neo with that role, and give it a password. Neo signs in as this user, so it sees only what the role allows.
4

Find the API host and the company ID

The company ID is the company name the client signs in to Dayforce with (Dayforce also calls it the client namespace). The API host is the host of the client’s Dayforce web services, such as us58-services.dayforcehcm.com. The client’s Dayforce administrator or Dayforce support gives it.

​
2. Add the connection in Neo

1

Open Integrations

In the Neo Dashboard, open Integrations → Dayforce, under Other.
2

Pick the client

In Customer, choose the client this Dayforce company belongs to. The client must be on your Companies tab. For a second client, click Add customer.
3

Save the connection

Choose the Environment (Production, unless you connect a Dayforce test company), and enter the API Host, the Company ID, the User Name and the Password. Click Save settings. Neo signs the user in and reads the client’s employee list before it saves, so a wrong value is rejected straight away, with what to fix.
When the web services user’s password changes, save the new one here. Neo loses access to that client’s Dayforce until you do.

​
3. Turn Dayforce on per agent

1

Open the agent's integrations

Open the agent in the Neo Dashboard and go to its Integrations tab.
2

Pick an access profile

Under Dayforce, pick an access profile, or set each permission group by hand.Read Only, Helpdesk and IT Admin keep Personal Details, Pay & Tax and Reports, Exports & Documents off. Turn one on only for an agent that needs it.

​
4. Start onboarding from new hires

To have Neo start onboarding from Dayforce, set up a scheduled agent that runs each morning: it lists each client’s employees with a hire date in the coming weeks, reads each new hire’s record, and creates their accounts, or opens the onboarding ticket your other agents work. Ask your Neo Support Agent to set it up, and say which clients, how far ahead to look, and what onboarding does for each client.