> ## 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. # Dayforce API > Find new hires and leavers in your clients' Dayforce, read each employee's job, department, location and manager, and write back their work email and Dayforce sign-in; personal details, pay, time, talent and reports when you turn them on The common use is onboarding from the HR system: a scheduled agent finds the employees with an upcoming hire date in a client's Dayforce, reads each one's record, creates their Microsoft 365 account with the values Dayforce holds, and writes the new work email back to Dayforce. Automatically enabled when you configure Dayforce permissions in your agent workflow. Dayforce is connected per client, so the agent calls the Dayforce company of the company it works on. ## What it does * Find employees by hire date, termination date, a change since a date, employee number, status or org unit * Read an employee's record with their work assignments, employment statuses, managers, locations, org units and contacts * Hire, rehire and change an employee, and change their contacts * Read and set an employee's Dayforce sign-in (SSO logins), roles, authorizations and security groups * Read and change the organization: org units, departments, jobs, positions and locations * Read and change personal details, pay and tax records, schedules, punches and time off, courses, certifications, skills and job postings * Run saved reports and bulk employee exports Neo does not upload a document's file or download one: the agent lists an employee's documents, and a person opens or adds the file in Dayforce. Neo replaces national identity numbers (such as social security numbers and PPS numbers), driver's licence numbers, bank account and routing numbers, pension fund membership numbers, clock PINs and the contents of document files (such as an earning statement PDF) in every Dayforce answer, so the agent never reads one. A write that sends Neo's placeholder back is refused, so Dayforce keeps the value it has. ## The parts of an employee record An agent can ask Dayforce for more of an employee record in one read, such as the work assignments and contacts with the employee. Each part it asks for needs that part's permission group: an employee's addresses need Personal Details, and their direct deposits need Pay & Tax. A hire or a change that writes a part needs that part's group at Read / Write, and asks a technician when that group asks. A search for employees by social security number needs Personal Details, and one by salary or pay rate needs Pay & Tax. ## Permission groups | Group | Access levels | Covers | | - | - | - | | Employees | Disabled, Read Only, Read / Write | The employee record (it holds the birth date and gender), work assignments, employment statuses with their pay rate, managers, locations, org units and contacts (work and personal email addresses and phone numbers); hiring and rehiring | | Accounts & Access | Disabled, Read Only, Read / Write | An employee's Dayforce sign-in (SSO logins), roles, authorizations, document security groups, clock device groups and pay adjustment code groups | | Personal Details | Disabled, Read Only, Read / Write | Home addresses, emergency contacts, dependants and beneficiaries, marital status, gender identity, ethnicity, disability, veteran status, health, identity documents and background screening | | Pay & Tax | Disabled, Read Only, Read / Write | Compensation, direct deposits, tax records, earning statements and pay summaries, pay runs and payroll imports, payroll elections, GL splits, payees and benefit carrier feeds | | Time & Scheduling | Disabled, Read Only, Read / Write | Schedules, punches, time off, availability, balances, labor demand and metrics, KPIs, operating hours and shift bids | | Talent & Recruiting | Disabled, Read Only, Read / Write | Courses, certifications, skills, training, performance ratings, HR incidents and policies, onboarding policies, unions, job postings and candidates | | Organization | Disabled, Read Only, Read / Write | Org units, departments, jobs, positions, location addresses, pay classes and types, employment statuses and reasons, contact types and projects | | Reports, Exports & Documents | Disabled, Read Only, Read / Write | Saved reports and analytics datasets, bulk employee exports, background job logs, data privacy history, documents and e-signature orders. A report or export can hold any field the Dayforce user sees | ## Access profiles | Profile | What runs on its own | What asks a technician | | - | - | - | | **Read Only** | Reads in Employees, Accounts & Access, Time & Scheduling, Talent & Recruiting and Organization | No write is allowed | | **Helpdesk** | The same reads | A change to an employee record, their contacts or their Dayforce sign-in | | **IT Admin** | Every read and write in those five groups but Accounts & Access | A change to an employee's Dayforce sign-in, roles or authorizations | | **Full Automation** | Every Dayforce call Neo sends, in every group | Nothing | Read Only, Helpdesk and IT Admin keep Personal Details, Pay & Tax and Reports, Exports & Documents off. Turn one on by hand for an agent that needs it. ## Safety Controls No Dayforce write always asks a technician: each one follows its group's approval setting and the agent's access profile. This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.