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

# Workday ATS setup

> What differs when configuring Workday Recruiting in Tenzo: workflow steps, WSDL-backed fields, and tenant XML namespace.

## What’s different about Workday

Most Tenzo ATS settings (stages, scoring, feedback, disposition, sync) work the same as other integrations. Workday adds a few things you must plan for:

| Topic                        | Why it matters                                                                                                                                                                            |
| ---------------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| **Stages vs workflow steps** | Workday can advance candidates by **workflow step**, not only **stage**. Eligibility and moves can depend on steps; step-based moves can override stage targets when both are configured. |
| **WSDL import**              | Custom field mappings that write into Workday are filled from your tenant’s **Recruiting WSDL** after a successful import. Until then, those pickers stay empty.                          |
| **Tenant XML namespace**     | Required when writing **application** custom fields that use **nested** WSDL paths so payloads use the correct tenant namespace.                                                          |
| **SOAP**                     | Some Workday behavior (including nested application objects and certain moves) goes through **SOAP**, not only REST-style configuration.                                                  |

Deeper pages: [Custom report for job fields](/ats-integrations/workday/custom-report-job-fields), [Workflow step cache](/ats-integrations/workday/workflow-step-cache), [Custom fields (WSDL)](/ats-integrations/workday/custom-fields-wsdl), [Tenant namespace](/ats-integrations/workday/tenant-namespace).

## Prerequisites

* Tenzo **Admin** and Workday **Recruiting** access to complete linking and tenant-side steps (per your org).
* Ability to **export the Recruiting WSDL** from Workday when you set up custom field mapping.

## Setup order (recommended)

<Info>
  Follow this **exact order** the first time through so workflow-step pickers, custom-field dropdowns, and candidate moves work without rework.
</Info>

<Steps>
  <Step title="Connect Workday">
    In **Admin → ATS Integrations**, add or open the Workday integration and complete linking for your tenant.

    Full walkthrough: [Connecting Workday to Tenzo](https://www.notion.so/Connecting-Workday-to-Tenzo-30afbc75865e807cbbbaddf2edec6a75).
  </Step>

  <Step title="Workflow steps (refresh cache, then configure)">
    **Workday-specific:** refresh the **workflow step cache** first, then set **Start Workflow Steps** and any per-transition workflow steps.

    * **Eligibility:** candidates match if they are in **Start Stages** *or* **Start Workflow Steps** (union, not intersection).
    * **Moves:** if a transition has **both** a stage and a workflow step configured, the **workflow step** is used for that move.

    [Workflow step cache](/ats-integrations/workday/workflow-step-cache)
  </Step>

  <Step title="Custom fields: WSDL import and tenant namespace">
    **Workday-specific:** import the **Recruiting WSDL**, set **Workday tenant custom XML namespace** when nested application paths apply, then complete **Custom Field Mapping**.

    Optional: if some **job** custom values only exist in reporting, configure a **JSON custom report** URL and credentials so Tenzo can merge those fields when loading jobs. [Custom report for job fields](/ats-integrations/workday/custom-report-job-fields)

    [Custom fields (WSDL)](/ats-integrations/workday/custom-fields-wsdl) · [Tenant namespace](/ats-integrations/workday/tenant-namespace)
  </Step>

  <Step title="Remaining ATS settings (stages, scoring, etc.)">
    Configure **Candidate flow stages**, **scoring**, **feedback**, **disposition**, **activity feeds**, and **sync** the way you would for any other integration—after workflow steps and custom fields are done, order no longer matters for Workday.
  </Step>
</Steps>

## Before production

* Workflow step cache refreshed with a **recent** run and **non-zero** count when you rely on steps.
* WSDL import done; custom field pickers show the fields you expect.
* Namespace set if you use nested application custom fields in mapping.
* Spot-check: one candidate’s eligibility, one move (stage or step), and one write to a mapped field.

## Related internal reference

[Workday ATS (internal)](/internal/ats/workday) — engineering notes and code pointers.