> For the complete documentation index, see [llms.txt](https://docs.siit.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.siit.io/integrations/hris/workday.md).

# Workday

<figure><img src="/files/rGfWK8SgTmD1uFfVLMqp" alt=""><figcaption></figcaption></figure>

Worker hierarchies, supervisory orgs, cost centers, and legal entities drive multi-entity workflows, including pre-boarding flows that fire 30 days before Day 1.

### What you get

* **Live People directory** — Workday workers (employees + contingent workers) appear in Siit with their full position data.
* **Lifecycle triggers** — Hire date, Termination date, Probation end, Work anniversary, and Birthday flow into Siit as workflow triggers.
* **Organization awareness** — Workday's supervisory, cost center, and location hierarchies are preserved so you can route, approve, and target by any org dimension.
* **Manager resolution** — the Workday supervisory hierarchy powers auto‑selected approvers.
* **Multi‑entity support** — legal entity, company, and region are synced and usable as conditions in workflows and audiences.

### What syncs from Workday

| Category        | Fields                                                                          |
| --------------- | ------------------------------------------------------------------------------- |
| Identity        | Preferred name, legal name, work email, Workday Worker ID, employee ID          |
| Role            | Job title, job profile, job family, job level, position ID                      |
| Org structure   | Manager, supervisory organization, cost center, location, company, legal entity |
| Employment      | Worker type (Employee / Contingent Worker), employment status                   |
| Lifecycle dates | Hire date, termination date, continuous service date, date of birth             |
| Custom          | Selected custom worker fields                                                   |

Work email is used as the canonical identifier.

### Before you connect

Workday requires more preparation than most HRIS platforms. You'll need:

* **Workday admin access** to configure an Integration System User (ISU) and a security group.
* The **tenant URL** (e.g., `https://wd5-impl-services1.workday.com/ccx/service/yourtenant`).
* Agreement with your Workday administrator on the scope of data exposed to Siit.

### Connect Workday

Workday setup is a two‑part process: prepare credentials in Workday, then paste them into Siit.

#### Part 1 — In Workday

1. **Create an Integration System User (ISU).** Create User → username `siit_isu`, set a strong password, and disable password expiration.
2. **Create a Security Group for the ISU.** Create a new **Integration System Security Group (Unconstrained)** named `Siit Integration`, and add the ISU as a member.
3. **Grant domain security policy permissions** (Get / Get All):
   * Worker Data: Public Worker Reports
   * Worker Data: All Positions
   * Worker Data: Workers
   * Manager: Worker Personal Data (for date of birth, if needed)
   * Organization Information (cost centers, supervisory orgs)
   * Any custom object/field you want exposed to Siit
4. Activate the pending security policy changes.
5. Locate and copy your **tenant URL** and **Workday REST API endpoint**.

> **Tip** — If your Workday admin is cautious, start with read‑only access to Public Worker Reports and add domains incrementally as you identify fields you need in Siit.

#### Part 2 — In Siit

1. Go to **Settings → Integrations**.
2. Find **Workday** in the HRIS section and click **Connect**.
3. Enter:
   * Tenant URL
   * ISU username and password
4. Click **Authorize**. Siit verifies the connection and runs an initial import.
5. Review the imported workers and field mapping, then click **Finish setup**.

### After the connection

* **Verify counts** — compare the number of workers in Siit with an "All Active Workers" report in Workday.
* **Set source of truth** — in **Settings → People → Fields**, make Workday the source for org‑structure fields (supervisory org, cost center, location, legal entity).
* **Map custom fields** — if Siit is missing a field you expect, check the ISU's domain permissions and add the field in the Siit mapping screen.
* **Build onboarding workflows** — Workday often becomes the trigger system for Day‑1 automation across IdP, apps, and equipment.

### Sync frequency

Workday data refreshes every few hours by default. For very large tenants, the schedule is tuned based on worker count. Manual syncs are available from **Settings → Integrations → Workday → Sync now**.

### Common workflows

**Pre‑boarding (30 days before start).** *Trigger: Start date − 30 days. Actions: send welcome email, notify manager to prepare a ready‑for‑Day‑1 checklist.*

**Day‑1 onboarding.** *Trigger: Hire date. Actions: create IdP account, assign baseline app bundle by supervisory org, ship laptop.*

**Offboarding on termination.** *Trigger: Termination date. Actions: revoke sessions, remove app access, equipment pickup request, notify manager.*

**Legal entity‑aware approval.** *Condition: Requester's legal entity = "Siit France SAS" → Approval from French IT lead; else from global IT lead.*

### Troubleshooting

**"401 Unauthorized" on connect.** The ISU password is wrong or the user has been locked. Reset the password in Workday and confirm the ISU isn't set to expire.

**Workers missing.** The ISU security group likely lacks access to a supervisory organization or a worker type. Ask your Workday admin to extend the group's scope.

**Custom field missing.** Make sure the custom field's domain is included in the ISU's security policy, then re‑map in Siit.

**Sync is slow or incomplete.** Very large tenants can hit Workday API throttling. Contact Siit support — we can adjust the sync strategy (incremental, chunked) for your tenant.

**Position vs. worker data.** Siit syncs worker‑level data by default. If you need position‑based attributes (e.g., position‑specific title), flag this during setup — we can enable position sync per tenant.

>
