---
title: "Workday Terminations, Transfers & Active OAuth Grants"
description: "Learn what happens to active user-delegated Workday OAuth 2.0 grants when an employee is terminated via Terminate Employee or transfers supervisory…"
url: https://kiweely.com/guides/workday-revoke-oauth-tokens-terminated-transferred-workers
---

# How Workday Terminations and Job Transfers Affect Active OAuth Grants

Completing Terminate Employee changes staffing status and security groups on the effective date, while disabling the Workday Account immediately kills active OAuth 2.0 refresh grants. Job transfers dynamically recalculate constrained supervisory permissions without requiring re-login.

-   **Checked** against Workday on November 15
-   Applies to **Workday Security & Lifecycle**
-   6 min read
-   Published November 15
-   By Kiweely

What happens to an employee’s external OAuth 2.0 access during offboarding or an internal transfer depends on two separate Workday mechanisms: **Workday Account status** (which governs whether OAuth credentials authenticate at all) and **effective-dated configurable security group membership** (which governs what rows and tasks an active credential can touch). Disabling a **Workday Account** immediately invalidates every user-delegated OAuth refresh grant (`invalid_grant`), whereas completing **Terminate Employee** or **Change Job** dynamically recalculates role-based and organization-constrained permissions on the effective date without waiting for tokens to expire.

## Lifecycle Event Matrix: What Happens to Active OAuth Grants?

When external apps use user-delegated OAuth ([registered via Register API Client](https://kiweely.com/guides/workday-register-api-client-vs-api-client-for-integrations)), Workday enforces lifecycle transitions automatically across REST, WQL, SOAP, and RaaS endpoints:

| Workday Lifecycle Event | Effect on Active Bearer Access Credential | Effect on Refresh Credential (`/token`) | Resulting API Data Access |
| --- | --- | --- | --- |
|  **Future-dated `Terminate Employee` approved today** | Remains valid until termination effective date | Remains valid until termination effective date | Normal active worker access until 11:59 PM prior to `Termination Date` |
|  **`Termination Date` reached (`Workday Account` Disabled / Expired)** | Rejected by Workday once session/account disables |  **Immediately invalid** (`400 {"error": "invalid_grant"}`) |  **Zero access** across all Workday APIs and UI |
|  **`Termination Date` reached (`Workday Account` left Active for alumni tax/pay)** | Valid only under post-termination security groups | Valid within `Refresh Token Timeout` unless revoked | Loses `Employee As Self` / `Manager` / `Role` groups; drops strictly to `Terminated` / retiree self-service domains (if any) |
|  **Involuntary immediate termination + manual `Edit Workday Account` -> `Account Disabled`** | Rejected immediately |  **Immediately invalid** (`invalid_grant`) |  **Instant cutoff** across external portals, AI connectors, and mobile apps |
|  **`Change Job` (supervisory org transfer or demotion from Manager to IC)** | Stays valid (no re-login needed) | Stays valid | Constrained `Manager` / `HR Partner` org scope recalculates dynamically to new org (or drops completely if no longer a manager) |
|  **Username changed on `Edit Workday Account`** | Existing session invalidated |  **Immediately invalid** (`invalid_grant`) | User must re-authenticate via `/authorize` under new username |

## Critical Trap: `Terminate Employee` vs. Disabling the Workday Account

In Workday, a **Worker** business object (`Employee` or `Contingent Worker`) is distinct from their **Workday Account** (`System Account`).

Running the **Terminate Employee** task ends the employee’s primary position on the **Termination Date**, triggers benefit and time-off adjustments, and removes active worker/role assignments. However, **completing `Terminate Employee` does not automatically disable the `Workday Account` unless you configure account deactivation**—because many enterprises intentionally leave former employees’ Workday Accounts active for 12 to 24 months in a restricted retiree/termed security group so alumni can download W-2s or final payslips.

### How to Enforce Immediate OAuth Cutoff for Involuntary Terminations

When an employee leaves involuntarily (or holds sensitive HR, Finance, or IT roles), do not wait for an end-of-day batch rule:

1.  Run **Edit Workday Account** for the worker (secured to the **Workday Accounts** domain in the **System** functional area) and select the **Account Disabled** check box—or set **Account Expiration Date** for planned departures.
2.  Confirm your **Termination** business process includes automated account expiration/disabling rules (via **Maintain Workday Account Provisioning** or custom step logic) aligned with `Primary Reason` (`Involuntary` vs. `Voluntary`).
3.  Include the **Auto-Manage Business Processes** service step on your **Termination** business process so in-progress **My Tasks** items (`Save for Later` drafts or pending approvals) are automatically canceled or reassigned rather than sitting attached to the terminated worker.
4.  For belt-and-suspenders assurance on high-privilege departures, open **View API Clients** -> **API Clients** -> **API Client > Manage Refresh Tokens** and revoke any active user-delegated refresh grants ([details in our refresh revocation guide](https://kiweely.com/guides/workday-oauth-refresh-token-expiration-rotation-revocation)).

## How Job Transfers (`Change Job`) Recalculate Constrained API Access

One of the strongest reasons to choose user-delegated OAuth over an Integration System User + external permission cache is how Workday handles internal mobility.

Suppose a manager leads `Supervisory Organization: Warehouse 4` on Monday and transfers via **Change Job** (plus **Assign Roles**) to lead `Supervisory Organization: Warehouse 9` effective Wednesday:

1.  User-delegated OAuth Bearer credentials carry **who** the caller is—they do **not** bake a static list of allowed employee IDs or org WIDs into a JWT claim.
2.  Every time an external app sends `Authorization: Bearer <access_credential>` to `GET /workers`, a WQL query, or a [custom RaaS report](https://kiweely.com/guides/workday-raas-user-delegated-oauth-vs-isu-basic-auth), Workday resolves the worker’s current role-based constrained security groups (`Manager`, `HR Partner`, `Cost Center Manager`) as of that request.
3.  On Wednesday morning—even if the manager never signed out of the external app and is still using the exact same OAuth grant—calling Workday returns rows for `Warehouse 9` and returns zero rows (or `403 Forbidden`) for `Warehouse 4`.

Propagation Timing on Security Group Changes

While staffing/role updates apply to interactive queries upon business process completion, Workday notes in Data Cloud / Live Data Query documentation that certain security group metadata caches can take up to 15 minutes to propagate across all query surfaces after a group change.

## Protecting Integrations and RaaS Reports When Admins Depart

Before deactivating the Workday Account of an HRIS analyst, integration developer, or report writer, run three pre-departure checks from the departing employee’s **Related Actions > Security Profile** menu so production integrations do not break overnight:

1.  **Custom RaaS Reports (`Security Profile > View Custom Reports`):** Run **Transfer Ownership of Custom Reports** to reassign web-service-enabled reports to an active `Report Writer` who holds access to the underlying data sources. Update external REST RaaS callers if they reference the `<report_owner>` username path segment.
2.  **Scheduled Background Processes:** Transfer ownership of scheduled report deliveries and EIBs to an active administrator or dedicated operational owner.
3.  **Never bind headless integrations to a human’s OAuth grant:** Verify in **View API Clients** ([audit guide](https://kiweely.com/guides/workday-view-api-client-audit-logs-sign-on-history)) that no scheduled middleware script is secretly running on a departing developer’s personal `Authorization Code Grant` refresh credential instead of a proper `Integration System User`.

## Offboarding & Transfer Verification Checklist

-   Test an involuntary termination in Sandbox: run **Terminate Employee** + check **Account Disabled** on **Edit Workday Account**, then replay the test worker’s previously captured Bearer and refresh credentials against `GET /workers/me` and `POST /token`. Confirm immediate `401` / `invalid_grant` rejection.
-   Test a lateral **Change Job** in Sandbox: move a test manager between two supervisory organizations and verify that an un-refreshed Bearer credential immediately reflects the new supervisory organization’s roster.

Because [Kiweely Bridge](https://kiweely.com/bridge/security) (coming next) and [Kiweely Leaf](https://kiweely.com/leaf) (coming next) store zero employee HR records at rest and execute every query live on Workday using each worker’s own user-delegated OAuth grant, every termination, account disablement, and job transfer you process in Workday takes effect across AI assistants and external employee apps automatically—with zero synced external shadow database left holding stale access.

## Frequently asked questions

### Does running Terminate Employee automatically disable the worker's Workday Account?

Not unless your Termination business process or account provisioning rules are configured to deactivate the account! Many tenants keep Terminated Employee self-service accounts active for W-2/payslip access unless explicitly disabled.

### What happens to a terminated worker's OAuth refresh token if their Workday Account stays active for alumni payslip access?

If the Workday Account remains active, OAuth tokens stay valid ONLY for the domains granted to Terminated Employee security groups (such as historical payslips)—all active Employee As Self, Manager, and HR Partner permissions drop off on the termination effective date.

### If a manager transfers from Warehouse 4 to Warehouse 9 via Change Job, can their existing OAuth token still read Warehouse 4?

No. User-delegated OAuth calls evaluate role-based constrained security groups dynamically in real time. Once the Change Job and role reassignment take effect, the existing token sees Warehouse 9 and loses constrained Manager access to Warehouse 4.

### What breaks if a terminated HR analyst owned custom RaaS reports or API refresh tokens?

User-delegated refresh grants tied to a deactivated account fail immediately with invalid\_grant. For RaaS custom reports owned by a departing analyst, run Transfer Ownership of Custom Reports to assign an active Report Writer before offboarding.

## Sources checked

-   [Workday Admin Guide — Terminate Employees](https://doc.workday.com/admin-guide/en-us/human-capital-management/staffing/hire-and-terminate/dan1370797153072.html)
-   [Workday Admin Guide — Concept: Termination Impact](https://doc.workday.com/admin-guide/en-us/human-capital-management/staffing/hire-and-terminate/hire-and-terminate-concepts/dan1370797453963.html)
-   [Workday Admin Guide — Deactivate Workday Accounts](https://doc.workday.com/admin-guide/en-us/authentication-and-security/accounts/workday-accounts/dan1370797411474.html)

## Related guides

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

-   [### Register API Client vs. Register API Client for Integrations in Workday Use Register API Client with Authorization Code Grant and PKCE when external apps act on behalf of a signed-in worker. Reserve Register API Client for Integrations for headless background jobs bound to a single Integration System User.](https://kiweely.com/guides/workday-register-api-client-vs-api-client-for-integrations)
-   [### Auditing External API Calls in Workday Sign-On History and Activity Logs Trace external Workday OAuth sign-ins and API requests using four native tools: Signons and Attempted Signons for auth events, View User Activity for 30-day read/write/download calls, View API Clients for client inventory, and View User or Task or Object Audit Trail for mutations.](https://kiweely.com/guides/workday-view-api-client-audit-logs-sign-on-history)
-   [### Calling Workday RaaS Reports with User-Delegated OAuth Instead of an ISU Replace shared Integration System User Basic authentication on Workday Reports as a Service (RaaS) with user-delegated OAuth 2.0 Bearer credentials so custom reports automatically enforce each signed-in worker’s row-level and field-level security.](https://kiweely.com/guides/workday-raas-user-delegated-oauth-vs-isu-basic-auth)
-   [### Managing Workday OAuth Refresh Token Expiration, Rotation, and Revocation Workday rotates user-delegated OAuth refresh tokens on every exchange while enforcing a fixed absolute Refresh Token Timeout measured from initial sign-in. Learn how access TTLs, Enforce 60 Minute Access Token Expiry, and admin revocation tasks work.](https://kiweely.com/guides/workday-oauth-refresh-token-expiration-rotation-revocation)

### More guides on Business processes and security

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

-   [Configuring Workday Pre-Hire Security So New Employees Can Complete Tasks Before Day One](https://kiweely.com/guides/workday-pre-hire-onboarding-access-before-day-one-security)
-   [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)
-   [Validating Country-Specific Address and Emergency Contact Formats in Workday Self-Service](https://kiweely.com/guides/workday-emergency-contact-home-address-change-validation-rules)
-   [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)

### From the blog on Business processes and security

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

-   [Why Copy-Pasting Workday Data into Consumer Chatbots Risks Client Data (and How Zero-Retention AI Fixes It)](https://kiweely.com/blog/workday-client-data-privacy-zero-retention-ai)
-   [Why Workday Business Processes Stall: The 5 Most Overlooked Routing Glitches](https://kiweely.com/blog/why-workday-business-processes-stall)
-   [Keeping External Workday Screens in Sync When You Change Absence Plans or Approval Rules](https://kiweely.com/blog/updating-custom-workday-screens-when-business-processes-change)

## 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.
