> ## Documentation Index
> Fetch the complete documentation index at: https://docs.neoagent.io/llms.txt
> Use this file to discover all available pages before exploring further.

# Connecting Dayforce to Neo

> Create a Dayforce web services user for a client and save it in Neo

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.

<Steps>
  <Step title="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.
  </Step>

  <Step title="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.
  </Step>

  <Step title="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.
  </Step>

  <Step title="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.
  </Step>
</Steps>

## 2. Add the connection in Neo

<Steps>
  <Step title="Open Integrations">
    In the Neo Dashboard, open [**Integrations** → **Dayforce**](https://dashboard.neoagent.io/integrations?open=dayforce), under Other.
  </Step>

  <Step title="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**.
  </Step>

  <Step title="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.
  </Step>
</Steps>

<Warning>
  When the web services user's password changes, save the new one here. Neo loses access to that client's Dayforce until you do.
</Warning>

## 3. Turn Dayforce on per agent

<Steps>
  <Step title="Open the agent's integrations">
    Open the agent in the Neo Dashboard and go to its **Integrations** tab.
  </Step>

  <Step title="Pick an access profile">
    Under **Dayforce**, pick an access profile, or set each permission group by hand.

    | Profile | What it does |
    | - | - |
    | **Read Only** | Reads employees, their jobs, Dayforce access, time, talent and the organization; changes nothing |
    | **Helpdesk** | Reads the same; a change to an employee's record, contacts or Dayforce sign-in asks a technician |
    | **IT Admin** | Changes employees, time, talent and the organization on its own; a change to an employee's Dayforce access asks a technician |
    | **Full Automation** | Every Dayforce call Neo sends, without approval, in every group |

    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.
  </Step>
</Steps>

## 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.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.