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 |
|---|---|---|---|
Worker Lifecycle StageCandidate / Unhired Pre-Hire (before Hire Completion) |
Assigned Self-Service Security GroupCandidate external career site account (if Recruiting) | Excluded Security Groups Until Start DatePre-Employee as Self, Employee as Self, All Employees |
Typical Permitted ActionsOffer acceptance, background check consent on external career site. |
Worker Lifecycle StageCompleted Future-Dated Employee Hire (Today < Hire Date) |
Assigned Self-Service Security GroupPre-Employee as Self |
Excluded Security Groups Until Start DateEmployee as Self, All Employees |
Typical Permitted ActionsOnboarding dashboard worklets, Contact Change, Personal Information Change, Complete Form I-9 (Sec 1), tax/payment elections, Review Documents. |
Worker Lifecycle StageCompleted Future-Dated Contingent Worker (Today < Contract Start Date) |
Assigned Self-Service Security GroupPre-Contingent Worker as Self |
Excluded Security Groups Until Start DateContingent Worker as Self, All Contingent Workers |
Typical Permitted ActionsContingent onboarding tasks, emergency contacts, NDA / policy Review Documents. |
Worker Lifecycle StageActive Worker on or After Start Date (Today >= Hire Date) |
Assigned Self-Service Security GroupEmployee as Self + All Employees (or Contingent equivalents) |
Excluded Security Groups Until Start DatePre-Employee as Self |
Typical Permitted ActionsFull 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:
- Mark
CompletionBeforeOnboarding: A future-dated hire only entersPre-Employee as Selfonce the Hire business process reaches its Completion step. PlaceOnboarding SetupandOnboardingafter the Hire Completion step. - Provision the Account Before
Onboarding: Place theCreate Workday Accountservice step (or your IdP provisioning integration that activates the account and sends welcome sign-in instructions to the personal address on file) before theOnboardingaction step. - Place
Onboarding SetupExactly One Step BeforeOnboarding: Workday pulls the Onboarding dashboard worklets, welcome people, and template settings fromOnboarding Setup(Create Onboarding Setup Templates) whenOnboarding Setupsits 1 step beforeOnboardinginside the staffing event. - Leave Security Groups Blank on the
OnboardingAction Row: Do not assign security groups to theOnboardingsubprocess row on theHiredefinition; Workday secures each step insideOnboardingindividually. - Avoid Duplicate Parallel Subprocesses: If
Change Benefit ElectionsorPersonal Information Changelives insideOnboarding, remove duplicate standalone copies fromHire—never runPersonal Information ChangeandOnboardingin parallel.
Sequenced cleanly, the tail of your Hire definition looks like this:
[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) |
|---|---|---|---|---|
| Functional AreaContact Information | Onboarding Subprocess / ActionContact Change or Home Contact Change |
Add Pre-Employee as Self to Initiating BP Policy?Yes | Required Self-Service Domain ( Modify Permission for Pre-Employee as Self )Self-Service: Home Contact Information (or granular Home Address, Home Email, Home Phone subdomains; omit Self-Service: Work Contact Information) |
HR / Admin Worker Data Domain ( View Minimum)Person Data: Home Contact Information |
| Functional AreaContact Information | Onboarding Subprocess / ActionName Change / Preferred Name Change |
Add Pre-Employee as Self to Initiating BP Policy?Yes | Required Self-Service Domain ( Modify Permission for Pre-Employee as Self )Self-Service: Legal Name, Self-Service: Preferred Name |
HR / Admin Worker Data Domain ( View Minimum)Person Data: Legal Name, Person Data: Preferred Name |
| Functional AreaContact Information | Onboarding Subprocess / ActionChange Emergency Contacts |
Add Pre-Employee as Self to Initiating BP Policy?Yes | Required Self-Service Domain ( Modify Permission for Pre-Employee as Self )Self-Service: Emergency Contacts |
HR / Admin Worker Data Domain ( View Minimum)Person Data: Emergency Contacts |
| Functional AreaPersonal Data | Onboarding Subprocess / ActionPersonal Information Change |
Add Pre-Employee as Self to Initiating BP Policy?Yes | Required Self-Service Domain ( Modify Permission for Pre-Employee as Self )Self-Service: Personal Data (and country-specific subdomains) |
HR / Admin Worker Data Domain ( View Minimum)Person Data: Personal Data |
| Functional AreaPersonal Data | Onboarding Subprocess / ActionEdit Government IDs / Edit Licenses |
Add Pre-Employee as Self to Initiating BP Policy?Yes | Required Self-Service Domain ( Modify Permission for Pre-Employee as Self )Self-Service: Government IDs, Self-Service: Licenses |
HR / Admin Worker Data Domain ( View Minimum)Person Data: Government IDs, Person Data: Licenses |
| Functional AreaOnboarding | Onboarding Subprocess / ActionComplete Form I-9 |
Add Pre-Employee as Self to Initiating BP Policy?Yes (Section 1) | Required Self-Service Domain ( Modify Permission for Pre-Employee as Self )Self-Service: I-9 Forms |
HR / Admin Worker Data Domain ( View Minimum)Worker Data: I-9 Forms |
| Functional AreaUSA / CAN Payroll | Onboarding Subprocess / ActionComplete Federal Withholding Elections |
Add Pre-Employee as Self to Initiating BP Policy?Yes | Required Self-Service Domain ( Modify Permission for Pre-Employee as Self )Self-Service: Payroll (My Withholding Elections) - USA (or - CAN) |
HR / Admin Worker Data Domain ( View Minimum)Payroll partner/admin domains |
| Functional AreaUSA Payroll | Onboarding Subprocess / ActionManage Payment Elections |
Add Pre-Employee as Self to Initiating BP Policy?Yes | Required Self-Service Domain ( Modify Permission for Pre-Employee as Self )Self-Service: Payment Election, Self-Service: Payroll (My Payment Elections) (or Payroll Interface (Payment Elections)) |
HR / Admin Worker Data Domain ( View Minimum)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 TemplateOpen 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 consolidatedTasksstep combiningContact ChangeandPersonal Information Change) but lacksModifyaccess 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:
- Step Delays (
Business Process -> Maintain Step Delay): On the related actions menu of any step inside theOnboardingbusiness process definition (for example, an ITTo Dostep orChange Benefit Electionsplaced after theOnboardingCompletion 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. - Pre-Hire Benefit Enrollment Matrix (
Change Benefits for Life Event):- Allow pre-hire benefit enrollment before start date: Add
Pre-Employee as Self(andPre-Contingent Worker as Selfif applicable) alongsideEmployee as SelfonChange Benefits for Life EventandSelf-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 Eventrestricted toEmployee as Self).
- Allow pre-hire benefit enrollment before start date: Add
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 inPre-Employee as Selffor the extra week and retains access to incomplete pre-hire tasks. - No-Show / Rescinded Hire (
RescindonHire): Rescinding theHireevent cancels in-progress Onboarding subprocesses; confirm yourManage Workday Accountsor Identity Provider lifecycle rule disables the provisionedWorkday Accountimmediately 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 Clientwith PKCE), Workday evaluates their token strictly underPre-Employee as Self. External onboarding checklists—such as day-one screens built with Kiweely Leaf (coming next) or guided Q&A via Kiweely 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.