---
title: "Workday Pre-Hire Onboarding Security Before Day One"
description: "How to configure Pre-Employee as Self, Create Workday Account, Onboarding Setup, step delays, and domain security so new hires finish tasks before day one."
url: https://kiweely.com/guides/workday-pre-hire-onboarding-access-before-day-one-security
---

# Configuring Workday Pre-Hire Security So New Employees Can Complete Tasks Before Day One

Future-dated completed hires in Workday belong to Pre-Employee as Self (or Pre-Contingent Worker as Self)—not Employee as Self—until their start date arrives. Synchronizing Hire step order, business process policies, and self-service domains unlocks pre-day-one tasks.

-   **Checked** against Workday on November 15
-   Applies to **Workday Staffing & Onboarding**
-   8 min read
-   Published November 15
-   By Kiweely

When a **Hire** event completes today for an employee whose start date is two weeks away, Workday does **not** place that person into `Employee as Self` or `All Employees`—it assigns them to **`Pre-Employee as Self`** (or **`Pre-Contingent Worker as Self`** for contingent workers) until 00:00 on their hire date. For incoming hires to sign in and complete contact details, Form I-9 Section 1, tax withholding, and policy acknowledgments before day one, four configurations must align: **Workday Account** provisioning timing, **Hire** business process step order, **Business Process Security Policies** on every subprocess, and **Self-Service Domain Security Policies**.

Missing even one half of a subprocess/domain pair leaves the incoming worker able to sign in to an empty Home page—or able to open a **My Tasks** item whose fields render read-only or blank.

## 1\. How Workday Transitions Pre-Hire Security Groups on Start Date

Workday strictly separates pre-start security membership from active worker membership (`Reference: Security Groups for Pre-Hires`):

| Worker Lifecycle Stage | Assigned Self-Service Security Group | Excluded Security Groups Until Start Date | Typical Permitted Actions |
| --- | --- | --- | --- |
|  **Candidate / Unhired Pre-Hire** (before `Hire` Completion) | Candidate external career site account (if Recruiting) | `Pre-Employee as Self`, `Employee as Self`, `All Employees` | Offer acceptance, background check consent on external career site. |
|  **Completed Future-Dated Employee Hire** (`Today < Hire Date`) |  **`Pre-Employee as Self`** | `Employee as Self`, `All Employees` | Onboarding dashboard worklets, `Contact Change`, `Personal Information Change`, `Complete Form I-9` (Sec 1), tax/payment elections, `Review Documents`. |
|  **Completed Future-Dated Contingent Worker** (`Today < Contract Start Date`) |  **`Pre-Contingent Worker as Self`** | `Contingent Worker as Self`, `All Contingent Workers` | Contingent onboarding tasks, emergency contacts, NDA / policy `Review Documents`. |
|  **Active Worker on or After Start Date** (`Today >= Hire Date`) |  **`Employee as Self`** + **`All Employees`** (or Contingent equivalents) | `Pre-Employee as Self` | Full employee self-service: Time Off, Time Tracking, Benefits, Expenses, Directory. |

Because `Pre-Employee as Self` has **zero** inherited permissions from `Employee as Self`, any security domain granted only to `Employee as Self` remains invisible to the new hire until midnight on day one. That isolation is a major security advantage: pre-hires cannot browse your internal org chart, company directory, or confidential intranet worklets before they actually start work unless you explicitly grant `Pre-Employee as Self` to a domain.

## 2\. Mandatory Step Sequence in `Hire` and `Onboarding` Business Processes

Before security groups even evaluate, the incoming worker needs an active `Workday Account` and an initiated `Onboarding` event (`Steps: Set Up Onboarding Business Process`, secured by `Business Process Administration` or `Manage: Business Process Definitions` in the *System* functional area).

Verify five structural rules on your **Hire** (and **Contract Contingent Worker**) business process definition:

1.  **Mark `Completion` Before `Onboarding`:** A future-dated hire only enters `Pre-Employee as Self` once the **Hire** business process reaches its **Completion** step. Place `Onboarding Setup` and `Onboarding` *after* the Hire Completion step.
2.  **Provision the Account Before `Onboarding`:** Place the **`Create Workday Account`** service step (or your IdP provisioning integration that activates the account and sends welcome sign-in instructions to the personal address on file) *before* the `Onboarding` action step.
3.  **Place `Onboarding Setup` Exactly One Step Before `Onboarding`:** Workday pulls the Onboarding dashboard worklets, welcome people, and template settings from `Onboarding Setup` (`Create Onboarding Setup Templates`) when `Onboarding Setup` sits **1 step before** `Onboarding` inside the staffing event.
4.  **Leave Security Groups Blank on the `Onboarding` Action Row:** Do **not** assign security groups to the `Onboarding` subprocess row on the `Hire` definition; Workday secures each step inside `Onboarding` individually.
5.  **Avoid Duplicate Parallel Subprocesses:** If `Change Benefit Elections` or `Personal Information Change` lives inside `Onboarding`, remove duplicate standalone copies from `Hire`—never run `Personal Information Change` and `Onboarding` in parallel.

Sequenced cleanly, the tail of your **Hire** definition looks like this:

text

```
[Hire Initiation & Approvals]
   -> [Completion Step] (Future-dated worker enters Pre-Employee as Self)
   -> [Service: Create Workday Account]
   -> [Action: Onboarding Setup] (Assigned to HR Partner / Manager — or auto-populated via template)
   -> [Subprocess: Onboarding] (Fans out pre-day-one Tasks, Review Documents, Form I-9, Withholding)
```

## 3\. Synchronizing Business Process and Domain Security Policies

To let a pre-hire complete an onboarding task, Workday checks **two** independent policy layers (`Steps: Set Up Security for Onboarding`):

-   **Business Process Security Policy** (`Edit Business Process Security Policies`): Grants permission to initiate or act on the subprocess step itself, plus **View Completed Only** under *Who Can Do Actions on Entire Business Process* (any pre-hire security group granted *View Completed Only* can view its future-dated events).
-   **Domain Security Policy** (`Edit Domain Security Policies`): Grants **Modify** (View + Modify) permission to read and edit the underlying fields inside that task.

Use this synchronization matrix across every subprocess included in your **Onboarding** business process:

| Functional Area | Onboarding Subprocess / Action | Add `Pre-Employee as Self` to Initiating BP Policy? | Required Self-Service Domain (`Modify` Permission for `Pre-Employee as Self`) | HR / Admin Worker Data Domain (`View` Minimum) |
| --- | --- | --- | --- | --- |
|  **Contact Information** | `Contact Change` or `Home Contact Change` | Yes | `Self-Service: Home Contact Information` (or granular `Home Address`, `Home Email`, `Home Phone` subdomains; **omit** `Self-Service: Work Contact Information`) | `Person Data: Home Contact Information` |
|  **Contact Information** | `Name Change` / `Preferred Name Change` | Yes | `Self-Service: Legal Name`, `Self-Service: Preferred Name` | `Person Data: Legal Name`, `Person Data: Preferred Name` |
|  **Contact Information** | `Change Emergency Contacts` | Yes | `Self-Service: Emergency Contacts` | `Person Data: Emergency Contacts` |
|  **Personal Data** | `Personal Information Change` | Yes | `Self-Service: Personal Data` (and country-specific subdomains) | `Person Data: Personal Data` |
|  **Personal Data** | `Edit Government IDs` / `Edit Licenses` | Yes | `Self-Service: Government IDs`, `Self-Service: Licenses` | `Person Data: Government IDs`, `Person Data: Licenses` |
|  **Onboarding** | `Complete Form I-9` | Yes (Section 1) | `Self-Service: I-9 Forms` | `Worker Data: I-9 Forms` |
|  **USA / CAN Payroll** | `Complete Federal Withholding Elections` | Yes | `Self-Service: Payroll (My Withholding Elections) - USA` (or `- CAN`) | Payroll partner/admin domains |
|  **USA Payroll** | `Manage Payment Elections` | Yes | `Self-Service: Payment Election`, `Self-Service: Payroll (My Payment Elections)` (or `Payroll Interface (Payment Elections)`) | `Worker Data: Payroll (Payment Elections)` |

After editing any domain or business process security policy, always run **`Activate Pending Security Policy Changes`** (`Security Configuration` domain)—unedited or unactivated policy changes have zero effect in the tenant.

> \[!TIP\] Auditing Policy Alignment with `View Business Process Template` Open the **View Business Process Template** report for **Onboarding** and inspect the **Task Security** tab. Workday highlights mismatches where a security group is authorized on a business process step (for example, a consolidated `Tasks` step combining `Contact Change` and `Personal Information Change`) but lacks `Modify` access on the corresponding Self-Service domain.

## 4\. Controlling What Waits Until Day One (`Maintain Step Delay` & Benefits)

Not every onboarding task belongs before day one. Company equipment sign-offs, badge activation, and sometimes medical benefit elections must wait until the worker physically starts. Workday gives you two precise controls:

1.  **Step Delays (`Business Process -> Maintain Step Delay`):** On the related actions menu of any step inside the `Onboarding` business process definition (for example, an IT `To Do` step or `Change Benefit Elections` placed after the `Onboarding` Completion step), configure a step delay anchored to the Hire effective date. Pre-day-one steps land in **My Tasks** immediately upon account creation; delayed steps dispatch automatically on day one.
2.  **Pre-Hire Benefit Enrollment Matrix (`Change Benefits for Life Event`):**
    -   **Allow pre-hire benefit enrollment before start date:** Add `Pre-Employee as Self` (and `Pre-Contingent Worker as Self` if applicable) alongside `Employee as Self` on `Change Benefits for Life Event` and `Self-Service: Benefits`.
    -   **Allow pre-hire Workday access for forms, but hold Benefits until day one:** Configure a step delay on benefit enrollment (or keep `Change Benefits for Life Event` restricted to `Employee as Self`).

## 5\. Rescinds, Start-Date Changes, and External API Behavior

Two edge cases deserve explicit testing in Sandbox before go-live:

-   **Start Date Pushed Back (`Correct Hire Date`):** If HR moves a completed hire’s start date from Monday the 1st to Monday the 8th before the 1st arrives, the worker remains in `Pre-Employee as Self` for the extra week and retains access to incomplete pre-hire tasks.
-   **No-Show / Rescinded Hire (`Rescind` on `Hire`):** Rescinding the `Hire` event cancels in-progress Onboarding subprocesses; confirm your `Manage Workday Accounts` or Identity Provider lifecycle rule disables the provisioned `Workday Account` immediately on rescind so pre-hire sign-in closes.
-   **User-Delegated OAuth APIs (`common/v1`, `person/v4`, `businessProcess/v1`):** When a pre-hire signs in via Workday OAuth 2.0 (`Register API Client` with PKCE), Workday evaluates their token strictly under `Pre-Employee as Self`. External onboarding checklists—such as day-one screens built with **[Kiweely Leaf](https://kiweely.com/leaf)** (coming next) or guided Q&A via **[Kiweely Bridge](https://kiweely.com/bridge)** (coming next)—automatically inherit the exact pre-hire boundaries you configured above, exposing permitted pre-boarding tasks while keeping internal company directories and post-start domains locked until day one.

## Frequently asked questions

### Why can't a future-dated new hire open Contact Change or Payment Elections even though Employee as Self has permission?

Until the hire effective date arrives, Workday assigns future-dated completed hires to Pre-Employee as Self (or Pre-Contingent Worker as Self) rather than Employee as Self or All Employees. Both the business process security policy and the corresponding Self-Service domain must include Pre-Employee as Self.

### What is the required step sequence inside the Hire business process to trigger pre-hire Onboarding?

Both Create Workday Account and the Hire Completion step must execute before Onboarding fires, and Onboarding Setup must sit immediately (one step) before the Onboarding subprocess step.

### How do we allow pre-hires to complete personal info and tax forms before day one while holding Benefit Enrollment until their start date?

Either omit Pre-Employee as Self from the Change Benefits for Life Event business process security policy, or configure Business Process -> Maintain Step Delay on the Change Benefit Elections step so it dispatches on or after the hire start date.

### Should we assign Pre-Employee as Self directly to the Onboarding action row inside the Hire business process?

No. Do not assign security groups to the Onboarding subprocess action row on Hire; Workday secures each step inside the Onboarding business process definition individually.

## Sources checked

-   [Reference: Security Groups for Pre-Hires](https://doc.workday.com/admin-guide/en-us/human-capital-management/staffing/pre-hire-tracking/ckb1520943781322.html)
-   [Steps: Set Up Security for Onboarding](https://doc.workday.com/admin-guide/en-us/human-capital-management/staffing/onboarding/onboarding-dashboard/dan1370797175242.html)
-   [Steps: Set Up Onboarding Business Process](https://doc.workday.com/admin-guide/en-us/human-capital-management/staffing/onboarding/onboarding-dashboard/dan1370797174813.html)

## Related guides

[All guides](https://kiweely.com/guides)

-   [### How to Run Role-Boundary Security Tests Across Employee, Manager, and HR Partner Personas Verify Workday security boundaries in Sandbox before rolling out reports, APIs, or external tools by combining four checks: View Security for Securable Item, Security Analysis for Securable Item and Account, Start Proxy UI checks, and user-delegated REST/WQL API readback.](https://kiweely.com/guides/workday-role-boundary-testing-employee-manager-hr-partner)
-   [### Preventing Accidental Indirect-Report Visibility in Workday Intersection Security Groups Managers and HR Partners see unintended indirect reports in Workday for two reasons: setting component Role-Based Security Groups to Current Organization and All Subordinates (COAS) instead of COO/COUS, or leaving component groups on domain policies alongside an Intersection Security Group.](https://kiweely.com/guides/workday-security-groups-intersection-subordinate-org-visibility)
-   [### Querying Pending Workday My Tasks and Inbox Approvals via API and WQL Retrieve pending Workday My Tasks items for the signed-in worker via GET /common/v1/workers/{ID}/inboxTasks, or query awaiting approvals with WQL data sources such as businessProcessTransactionsAwaitingMyAction and businessProcessStepsAwaitingMe alongside businessProcess v1 REST calls.](https://kiweely.com/guides/workday-inbox-my-tasks-awaiting-action-rest-wql)
-   [### Validating Country-Specific Address and Emergency Contact Formats in Workday Self-Service Workday validates home addresses, phone numbers, and emergency contacts by country—enforcing required components, extended street/house-number splits, Google libphonenumber rules, and exact Primary Priority = 1 constraints across UI tasks and REST/SOAP APIs.](https://kiweely.com/guides/workday-emergency-contact-home-address-change-validation-rules)

### More guides on Business processes and security

[All 27 guides](https://kiweely.com/guides#business-processes)

-   [Tuning Workday Business Process Notifications When Using External Mobile or Chat Approvals](https://kiweely.com/guides/workday-notification-delivery-settings-suppressing-duplicate-emails)
-   [Workday Time Off vs. Leave of Absence: Helping Employees Pick the Right Request Type](https://kiweely.com/guides/workday-leave-of-absence-vs-time-off-employee-request-routing)
-   [How to Trace Who Approves a Leave or Expense Request in a Workday Supervisory Org](https://kiweely.com/guides/workday-find-approver-chain-supervisory-org-business-process)
-   [How Workday Task Delegation Works When Managers Approve Through APIs](https://kiweely.com/guides/workday-delegation-rules-external-approvals-acting-on-behalf)
-   [Why Workday Says ‘This Task Is Not Available’ or ‘Waiting on Initiator’ on a Business Process Step](https://kiweely.com/guides/workday-business-process-this-task-is-not-available)
-   [Why Can’t a Security Group See a Workday Dashboard or Worklet After You Added Permission?](https://kiweely.com/guides/workday-worklet-dashboard-not-visible-security)
-   [What does rescinded mean in Workday? Rescind vs cancel vs correct, and when each applies](https://kiweely.com/guides/workday-business-process-rescind-cancel-correct)
-   [Workday custom validations and condition rules: block bad data with Critical or Warning severity](https://kiweely.com/guides/workday-custom-validations-condition-rules)

### From the blog on Business processes and security

[All posts](https://kiweely.com/blog)

-   [Designing Privacy-Safe Mobile Push Notifications for Workday Approvals and Pay Updates](https://kiweely.com/blog/privacy-safe-push-notifications-for-workday-tasks-on-phones)
-   [Why Building Internal Workday Apps in Retool or Lovable Stalls on OAuth and Security](https://kiweely.com/blog/retool-superblocks-lovable-on-workday-oauth-trap)
-   [How Submitting Workday Time Off from Claude or ChatGPT Works Safely End to End](https://kiweely.com/blog/submitting-workday-time-off-from-claude-chatgpt-with-approval)

## Let Workday check the work.

Kiweely writes WQL and builds orchestrations in your own tenant, and Workday, not Kiweely, says whether they passed.

[Start for free](https://kiweely.com/download) [See how it works](https://kiweely.com/vine/how-it-works)

## Get the next guide in your inbox.

One email a month with new guides and one Extend tip. Nothing else.
