---
title: "Day-One Access and Last-Day Revoke Without One Shared…"
description: "Give each Workday identity feed its own integration user, and time the Okta or Entra revoke to the termination Workday actually stored."
url: https://kiweely.com/blog/day-one-access-and-last-day-revoke-without-one-shared-account
---

# Day-One Access and Last-Day Revoke Without One Shared Account

Workday’s own guidance is one integration system user per integration, with only the domains that feed needs. Okta and Entra each have a documented way to revoke on the termination date, and both can fire a day early or a day late if you ignore their time rules.

-   By Kiweely
-   November 16
-   4 min read

The account that reads Workday for a joiner feed should not be the account that can read payroll. Workday’s integration course says that outright. Okta and Microsoft Entra then decide when “day one” and “last day” happen, and those products do not use the calendar date on the termination screen by itself.

## One integration, one user

[Workday Configurable Security](https://doc.workday.com/workday-education/en-us/course-manuals/creating-and-securing-integrations/workday-configurable-security.html) gives the reasons an integration system user exists. A person quits, changes jobs, or is promoted, and their security changes with them. An integration system user is not a person, does not need the Workday interface, and is configured once. The course’s rule is one integration system user and one integration system security group per integration system. That user gets the domains for that integration. The stated purpose is to prevent an overpowered account and to keep the integration from missing data a human user cannot see.

Unconstrained means the user can see every worker. Constrained means the organizations you assigned. Most connector setups in that course use unconstrained. A joiner feed that only needs workers in one company is the case for constrained. Connectors that use the Data Initialization Service need the Integration Event domain, plus the domains on any field override or eligibility criteria. [Securing Connectors](https://doc.workday.com/workday-education/en-us/course-manuals/creating-and-securing-integrations/securing-connectors.html) says that. Benefits and payroll together means the user needs both product areas, which is a reason to keep the identity feed’s user off the payroll domains. [Enhance Benefits Connectors](https://doc.workday.com/workday-education/en-us/course-manuals/creating-benefits-connector-integrations/enhance-benefits-connectors.html) recommends the security group per product area and the user per integration system, then a launch you compare with a functional report.

A shared user that can launch every feed is the account the course is written to retire. Split the Okta or Entra reader from the payroll extract and from the 834. Test each launch as that feed’s user. If the file is short, the domain is missing. If the file contains pay, the identity user is too wide.

## When access starts and when it stops

Okta’s Workday page, [https://help.okta.com/en-us/content/topics/provisioning/workday/workday-provisioning.htm](https://help.okta.com/en-us/content/topics/provisioning/workday/workday-provisioning.htm) , documents both edges:

-   Pre-Start Interval imports a user before the Worker/Employee Date when Workday’s PreHire Date falls inside the interval. Profile sourcing has to be on. The interval says when someone becomes eligible for an early import. It does not say the import will run at that minute. The same interval also pulls other future-dated updates forward, except values that come from custom reports. If you want early hires and you do not want every future attribute change, Okta says to import those attributes from custom reports.
-   Deactivation during import looks back 24 hours and forward 24 hours. An immediate termination reason, matched with a regular expression to Workday’s termination subcategory ID, deactivates the worker immediately. Otherwise Okta compares the termination or last day worked with the current time, using the time zone Workday put on the date. Okta says that value is typically midnight Pacific. If now is after that instant, the user is deactivated.
-   A future termination whose reason matches the immediate list is deactivated one day early. Okta’s example is a termination date of 22 October processed on 21 October.
-   Real Time Sync is the business-process trigger for a termination that should not wait for the next import. The reason still has to match, and the termination date has to be the current date.

Entra’s side is the termination lookahead and the future-hire query, documented at [https://learn.microsoft.com/en-us/entra/identity/app-provisioning/configure-workday-termination-lookahead](https://learn.microsoft.com/en-us/entra/identity/app-provisioning/configure-workday-termination-lookahead) and [https://learn.microsoft.com/en-us/entra/identity/app-provisioning/workday-integration-reference](https://learn.microsoft.com/en-us/entra/identity/app-provisioning/workday-integration-reference) . The integration system user Microsoft describes runs in Pacific Time, so a last day in a zone ahead of Pacific is late unless the 24-hour lookahead is on. Future-dated hires are read as of the hire date, which returns Active 1, so the account can exist before the person starts unless a DateDiff expression keeps it disabled. Incremental sync will also miss attributes that never hit the worker transaction log. That miss is [the incremental sync guide](https://kiweely.com/guides/why-workday-to-entra-incremental-sync-misses-changes).

Day one, in other words, is either the hire date you mapped or an earlier pre-start window you turned on. Last day is the termination instant after the product’s time-zone rule, the lookahead, and any “immediate reason” that fires a day early. Write those three down for the feed. A ticket that says “revoke at 5 p.m. local” is not what either connector does out of the box.

The match key still decides whose access you are granting. Employee ID, contingent worker ID, and universal ID are different Workday sequences. [Match on the ID that survives the job change](https://kiweely.com/guides/match-workday-workers-to-okta-on-the-right-id).

## What Roots publishes for this feed

[Kiweely Roots](https://kiweely.com/roots) (coming next) lists Okta, Microsoft Entra ID, and ServiceNow as identity systems it joins on day one and closes on the last. The directory rule is: fix the feed, test it, turn it back on, and send the owner a note. That is a different gate from payroll, benefits, and tax, which are proven on Sandbox with the failed rows and then wait for approval. You choose the gate per integration.

Each integration has its own API client, scoped to what it reads. That is the Roots wording for the split Workday already recommends with integration system users. The run keeps times, counts, and outcomes, and drops the records. Agents design, build, test, and fix the integration. The integration that runs is tested code. Claude, ChatGPT, and Gemini can ask Roots, over MCP, whether a joiner ran. A payroll change requested in the same breath still waits.

Roots is coming next. Register interest at [kiweely.com/roots](https://kiweely.com/roots) and say which feed is still on one shared Workday user. The page does not claim that a directory repair skips the test, and it does not claim a last-day revoke in a local time zone the Okta or Entra setting does not implement.

## Read next

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

-   [November 16 ### Workday Data Cloud, Snowflake, and the Feeds Roots Still Fits](https://kiweely.com/blog/workday-data-cloud-snowflake-vs-operational-feeds)
-   [November 16 ### Kiweely Roots vs MuleSoft, Boomi, and Workato for Workday](https://kiweely.com/blog/kiweely-roots-vs-mulesoft-boomi-workato)
-   [November 16 ### What a Role-Safe Workday Tool Catalog Looks Like for HR Partner and Employee as Self](https://kiweely.com/blog/role-safe-workday-tool-catalogs-hr-partner-vs-employee)

### More guides on More Workday guides

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

-   [Full File or Changes-Only 834 After Workday Open Enrollment](https://kiweely.com/guides/workday-834-full-file-or-changes-only-after-open-enrollment)
-   [Match Workday People to Okta on the ID That Survives the Job Change](https://kiweely.com/guides/match-workday-workers-to-okta-on-the-right-id)
-   [Why a Delivered Workday File Was Still Rejected](https://kiweely.com/guides/workday-file-delivered-carrier-rejected-rows)
-   [Scoping AI Workday Access for Contingent Workers and Alumni](https://kiweely.com/guides/scoping-ai-workday-access-contingent-workers-alumni)
-   [Correlating Workday Audit Events with AI Assistant Tool Calls](https://kiweely.com/guides/correlating-workday-audit-with-ai-assistant-calls)
-   [Workday Cost Centers and Workers to NetSuite After a Reorg](https://kiweely.com/guides/workday-cost-centers-workers-to-netsuite)
-   [Workday Headcount to Snowflake When Data Cloud Is Not Enough](https://kiweely.com/guides/workday-headcount-to-snowflake-beyond-data-cloud)
-   [Performance Check-In and Goals Screens Managers Will Open](https://kiweely.com/guides/performance-check-in-goals-screens-managers-open)

## Your Workday work, done by AI.

Kiweely Vine is the AI agent that builds, deploys and tests Extend apps as real people, makes changes in any Workday task screen, answers from your real tenant and builds reports.

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

## Get the next one in your inbox.

One email a month for Workday teams: what’s changing in Workday and what to retest, one tip tried in a real tenant, and what’s new at Kiweely.
