> ## Documentation Index
> Fetch the complete documentation index at: https://docs.iru.com/llms.txt
> Use this file to discover all available pages before exploring further.
# Connect Workday
> Connect Workday to Iru Identity so it reads workers from a custom report and keeps your Iru directory in sync as people are hired, transferred, or terminated.
Connecting **Workday** lets Iru pull worker records straight from a Workday report
and keep your [directory](/en/identity/directory/directory-overview) in sync - when
someone is hired, changes departments, or leaves, those updates flow into Iru on
their own.
This page covers the Workday-specific steps. For the concepts shared across
Directory Sync - the unique identifier, required fields, IQL, and what happens on
each sync - see
[Directory Sync](/en/identity/directory/directory-sync).
## 1. Choose Workday
In **Directory → Sync**, select **Connect Source** and pick **Workday**.
## 2. Connect your Workday account
Give the connection a **name** and an optional **description**, then **Connect**. A
Workday window opens where you sign in - you'll enter your **Workday tenant**, then
the **username and password** for the integration account. When Workday confirms
the connection, the window closes and Iru continues.
Use a dedicated Workday integration account rather than a personal login, so the
connection keeps working as people come and go.
## 3. Point Iru at your report
Enter the **report name** and the **integration user** that should run it.
Workday exposes worker data through a custom report you build on your side (a
report enabled as a web service). This tells Iru *which* report holds the people to
import and *which* account to run it as. Everything Iru imports comes from the
columns in that report - so make sure it includes every field you care about
(email, name, department, manager, employee ID, and so on).
## 4. Map your data to Iru
Iru reads your report's columns and lays them out to match to Iru attributes.
* **Set a unique identifier** - choose the column that uniquely identifies each
person, usually an **employee ID**. Once you save the connection, it can't be
changed.
* **Map the required attributes** - **email, first name, last name, and username**
must be mapped; everything else is optional.
* **Transform with IQL when needed** - pick a column, or write a short IQL
expression to build a value. Iru suggests your report's column names and checks
the expression as you type.
Examples (illustrative - use your report's own column names):
* Build a username from an email: `email_work.split("@")[0]`
* Combine two columns: `first_name + " " + last_name`
* Prefer one column, fall back to another: `optional.ofNonZeroValue(email_work).orValue(email_home)`
See [Map your data](/en/identity/directory/directory-sync#map-your-data) for more
on mapping, including the safe pattern for sometimes-blank fields.
## 5. Finish and turn it on
Save your mappings. You'll land on the connection's detail page - review
everything, then **Enable**. A connection starts **disabled**, so enabling it kicks
off the first import and keeps Iru in sync.
On the detail page you can later **re-authenticate**, **edit your report or
mappings**, **force an attribute sync** to re-read the latest report columns, and
**review activity, effective users, and sync errors**.
## Related
The shared concepts behind every Directory Sync provider.
The other supported HR system - simpler, with no report step.