Skip to content
KiweelyKiweelyKiweely

Pre-Hire Windows That Create Directory Users Before Anyone Is Hired

Workday keeps pre-hires on their own ID sequence until Hire or Contract Contingent Worker. Okta imports them when a pre-start interval covers the PreHire Date. Entra reads future hires as of the hire date and gets an active profile.

  • Checked against Workday on
  • Applies to Workday Extend
  • 6 min read
  • Published
  • By Kiweely
On this page

A directory user for someone Workday has not hired is usually a pre-hire, read early on purpose. Workday keeps that person off the employee record until Hire Employee or Contract Contingent Worker. Okta and Microsoft Entra both have a switch that pulls the person in before that date. Leave the switch on without a rule for the account’s enabled state, and the company gets an account that can sign in before there is an employee.

What a pre-hire is in Workday

Steps: Manage Pre-Hire Tracking is the setup: create a pre-hire one at a time or load a group with a web service, consider the pre-hire for a job or position, and record interview results. Change Hire Eligibility Status marks people who must not appear on Hire Employee or Contract Contingent Worker. They remain visible on the Pre-Hires Ineligible for Hire report. Delete Pre-Hires removes the record. None of these steps create an employee.

Edit Personal and Contact Information for Pre-Hires says Workday uses the pre-hire’s ID, personal information, and contact information if you later hire them or contract them. You can edit personal information and IDs only after the pre-hire is considered for at least one position. Public contact information is what directories and listings show. After the hire, you cannot keep editing personal information on the pre-hire record. You edit the employee. A feed that is still pointed at the pre-hire record after that moment is reading a record Workday has stopped updating.

National and tax IDs are a separate caution. The same page says Social Security Number is a national ID type, and that a tax ID is required if you hire the person. A provisioning file does not need the national ID to create a directory account. Leave it off the integration system user’s domains unless a downstream system has a real reason to store it.

Steps: Set Up Workday IDs gives pre-hires their own sequence generator, distinct from employees and contingent workers. A universal ID is the optional value that follows the person across pre-hire, employee, prospect, and student. If you do not set it, the pre-hire ID and the later employee ID are two values. FAQ: How do I import worker IDs during a hire? is how an external ID becomes the employee ID: Verify Proposed Employee ID on the Hire business process, fed by Put Hire Event Proposed Worker ID. Without that step, the employee sequence runs on its own.

The Okta window

Okta documents Pre-Start Interval on https://help.okta.com/en-us/content/topics/provisioning/workday/workday-provisioning.htm . It is optional, and it requires profile sourcing. The interval is how many days before the Worker/Employee Date Okta will consider the user. Okta evaluates Workday’s PreHire Date. If that date falls inside the interval, Okta imports the user. If the PreHire Date is further out than the interval, Okta waits until the window opens. A seven-day interval and a PreHire Date seven days before the start date imports the account. A PreHire Date eight days out does not, until the window moves.

Okta also says a non-zero interval imports other future-dated user updates early. A provisioning-group change effective in two days is applied after the next import when the interval is three. Termination dates, and attributes imported through custom reports, ignore the interval. If you need the early account and you need other attributes to stay on their effective dates, Okta’s instruction is to bring those attributes in from custom reports and to drive groups from those attributes.

The duplicate is the other half of the same page. With a pre-hire interval and no universal ID, Okta imports the contractor and the future full-time pre-hire as two Workday IDs and shows a duplicate on the Import tab. Universal ID, configured in Workday, lets Okta filter a pre-hire that matches an active worker. Universal ID applies to workers created after you configure it, unless you update existing profiles. The match-key detail is employee ID versus universal ID.

The Entra window

Microsoft’s Workday integration reference, https://learn.microsoft.com/en-us/entra/identity/app-provisioning/workday-integration-reference , says future-dated hires in Workday have Active set to 0 until the hire date. The connector queries the hire as of the hire date and time, so the profile it stores has Active 1. Microsoft describes this as a way to fill in the directory profile in advance. The same note says to use DateDiff when the account should stay disabled until the start date.

A future-dated conversion from contingent worker to employee is processed when it is entered, not on the effective date, unless you add the filter Microsoft describes in that section. The person can show full-time attributes while the contingent worker assignment is still the one in effect. That is a second kind of early account: the right person, the wrong profile, ahead of the effective date.

Entra’s incremental cycle will not repair an attribute that never appears on the worker transaction log. If the pre-hire’s location lives on a related object, the early account can keep a blank or stale location until a full sync. See incremental sync misses.

A window you can explain

Record in Workday Directory outcome you can defend Outcome that becomes a phantom
Record in WorkdayPre-hire, not yet considered for a position Directory outcome you can defendNo account. Personal-information edits are not even available until they are considered. Outcome that becomes a phantomAn import of every pre-hire, including people marked ineligible for hire.
Record in WorkdayPre-hire inside a deliberate pre-start interval, account disabled until the employee date Directory outcome you can defendAn account that exists for equipment and access requests, and cannot sign in. Outcome that becomes a phantomThe same import with the account enabled, or with the pre-hire ID as the only match key.
Record in WorkdayHire completed Directory outcome you can defendThe employee ID, or the proposed ID you imported, is the match key. Further personal-data edits happen on the employee. Outcome that becomes a phantomA second account, because the pre-hire sequence and the employee sequence both matched as “new.”
Record in WorkdayPre-hire deleted, or marked ineligible Directory outcome you can defendThe directory account is disabled or removed by a rule you run on purpose. Outcome that becomes a phantomThe account remains, because the feed only creates.

Ineligible pre-hires do not show on Hire Employee. They do not disappear from a feed that queries pre-hires without that status. Include the eligibility status in the population, or accept accounts for people the recruiters have already rejected.

The integration system user for this feed needs pre-hire domains only if you intend to read pre-hires. Worker Data domains that also expose pay do not belong on a joiner feed. One user per integration is the Workday course’s rule, and it is the point of day-one access without one shared account.

Where Roots fits

Kiweely Roots (coming next) describes identity as joined on day one and closed on the last. That is a later moment than a pre-hire window. A directory feed in Roots is fixed, tested, and turned back on, with a note to the owner. Each integration has its own API client, scoped to what it reads, which is how a joiner feed stays off national IDs and pay. Register interest on the Roots page and say how many days before a start date you actually want an account. Roots does not turn a pre-hire into an employee. Hire Employee still does that.

Questions to settle with whoever owns the directory

We need the laptop imaged before Monday.

Use a pre-start interval or a future-hire query, keep the account disabled until the employee date, and match on a universal ID so Monday’s hire updates that account. Okta’s interval and Entra’s DateDiff are the documented controls.

Recruiting loaded a web-service file of pre-hires and the directory filled up.

That file is Create Pre-Hires by web service, or an equivalent load. The directory population has to exclude pre-hires who are ineligible or not yet inside the interval. Deleting the pre-hire in Workday does not, by itself, delete a directory user a previous import already created.

The person started and now has two accounts.

Compare the pre-hire sequence with the employee sequence. Configure universal ID for new workers, and update the existing person if Okta or Entra is supposed to recognize them as one. Then disable the extra account in the directory. Workday will not merge those two IDs after the fact except through the universal ID you assign.

Sources checked

Let Workday check the work.

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

Get the next guide in your inbox.

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

We’ll email you once to confirm. Unsubscribe in one click from any issue.