---
title: "Scoping AI Workday Access for Contingent Workers and Alumni"
description: "How Workday already separates contingent workers, employees, and terminated workers, and what a user-delegated assistant inherits."
url: https://kiweely.com/guides/scoping-ai-workday-access-contingent-workers-alumni
---

# Scoping AI Workday Access for Contingent Workers and Alumni

Contingent Worker as Self and Employee as Self are limited to the person’s own data. Terminee as Self is the self-service group for terminated workers. Former Worker Storage is a different population. A user-delegated assistant cannot see more than that sign-in already can.

-   **Checked** against Workday on November 16
-   Applies to **Workday Extend**
-   5 min read
-   Published November 16
-   By Kiweely

Scoping AI Workday Access for Contingent Workers and Alumni

The assistant should not be the system that decides who is an employee. Workday already did that, with security groups. A user-delegated connection asks Workday as the person who signed in. If that person is a contingent worker, a terminee, or someone with no account, the assistant does not get a better seat.

[Kiweely Bridge](https://kiweely.com/bridge) (coming next) is built that way: **Register API Client** for the worker, not an integration system user. Admin policy can remove tools and fields. It cannot grant a domain the worker does not have.

## The groups Workday already assigns

[Security Group Membership](https://doc.workday.com/workday-education/en-us/course-manuals/security-for-administrators/security-group-membership.html) separates the groups people confuse in an AI rollout:

| Group | How membership happens | What the constraint is |
| --- | --- | --- |
| Employee as Self, Contingent Worker as Self, Terminee as Self, Retiree as Self | Workday-assigned self-service | That person’s own data |
| All Employees, All Contingent Workers, All Retirees, All Terminees | Workday-assigned public groups | Public data, not every private field |
| HR Partner and other role-based groups | Derived from a role on a position or job | Target data in the organizations where the role is assigned |

[Security groups for pre-hires](https://doc.workday.com/admin-guide/en-us/human-capital-management/staffing/pre-hire-tracking/ckb1520943781322.html) adds a timing detail: a future-dated hire is **Pre-Employee as Self** or **Pre-Contingent Worker as Self**, not All Employees or All Contingent Workers, until the hire or contract date.

Self-service domains the education manual gives as examples include home address, emergency contacts, and beneficiaries. Public domains it names include **Worker Data: Public Worker Reports**. Putting a contingent worker in All Contingent Workers does not hand them employee compensation. Putting an employee assistant on a shared integration user would. Do not do that second thing and then try to filter it in the prompt.

## Contingent workers

Scope the assistant the way you already scoped expense reports. The education manual’s example is an expense-report business process that starts out for employees only. Extending it means adding **Contingent Worker as Self** to that business process and to the related domains. Until you do, a contingent worker’s sign-in cannot run the task, and a user-delegated assistant cannot run it either.

Some domains refuse whole classes of security group. The same manual says certain domains restrict which security-group types may be granted access. Check the domain before you “turn on chat for vendors” by dropping All Contingent Workers onto a worker-data domain.

Private contact data is the usual overshare. [Access to worker information](https://doc.workday.com/admin-guide/en-us/human-capital-management/worker-information/contact-and-personal-information/contact-information/dan1370797390310.html) says a home address stays private unless it is also the work address and you mark it public. **Person Data: Home Contact Information** and **Person Data: Work Contact Information** reach both public and private contact data. Workday’s recommendation on that page: do not assign **All Users, All Employees, All Contingent Workers, or All Retirees** to those domains if private contact data should stay limited. An intersection security group can narrow directory access further so only specific roles see it.

Bridge (coming next) still only helps after that review. Field redaction can strip a field the domain returned. It is not a substitute for the domain.

## Alumni and terminated workers

“Alumni” is not a Workday security group name on these pages. The documented populations are:

**Terminated workers who still sign in.** [FAQ: Terminations](https://doc.workday.com/admin-guide/en-us/human-capital-management/staffing/hire-and-terminate/bwz1497990098885.html) says to put them in **Terminee as Self** and add that group to the self-service domains you want them to keep. The page’s primary domains for benefits, pay, and personal data are **Self-Service: Benefits**, **Self Service: Benefits and Pay Hub**, **Self-Service: Compensation**, and **Self-Service: Personal Information**. It also lists narrower domains such as payslips, tax documents, home contact, and emergency contacts. If Terminee as Self is not on a domain, the alumnus does not see it in Workday, and the assistant does not either.

**Other people looking up terminated workers.** The same FAQ says you need **Worker Data: Public Worker Reports** plus at least one more domain, and it lists examples that include **Worker Data: Compensation by Organization**, **Worker Data: Benefit Elections**, **Self-Service: Benefit Elections**, and **Person Data: Personal Information**. An HR Partner who can see terminated compensation in their organizations will still see it through a user-delegated call. An employee who cannot see it in the UI will not see it in chat.

**Former workers loaded at implementation.** [Rehire Former Workers](https://doc.workday.com/admin-guide/en-us/human-capital-management/worker-information/former-workers/dan1385073237213.html) uses “former worker” for people terminated before you implemented Workday, stored so you can rehire them. Access is the **Former Worker Storage** domain. That is not the alumni population of people who worked in the tenant and then left. Do not grant an assistant broad former-worker storage because a slide said “alumni.”

Someone with no Workday account cannot complete a user-delegated sign-in. Bridge never sees the password or the MFA factor; the person signs in on Workday. No account means no grant. A shared integration user would hide that fact. The user-delegated design does not.

## A rollout check

1.  List who may ask questions: employees, contingent workers, terminees, retirees. Map each to the self-service group above.
2.  For each group, read the domains on **Domain Security Policies for Functional Area** rather than guessing from the chat tool name.
3.  Confirm All Contingent Workers and All Terminees are not on private contact domains.
4.  In a non-production tenant, sign in as a contingent worker and as a terminee and ask for someone else’s pay and for their own. The own-data answer may be legitimate. The other person’s answer should fail the same way the UI fails.
5.  Enable writes only for tasks that group can already submit, and only behind the browser confirmation Bridge uses when a write is enabled.

[Register interest](https://kiweely.com/bridge). Kiweely Bridge is coming next. The security groups in this guide are already yours to fix, with or without it.

## Frequently asked questions

### Can a contingent worker’s chat show employee pay if the prompt demands it?

Only if that contingent worker’s Workday security can already open employee pay. Self-service membership does not. A role assignment might. The prompt does not.

### Is Terminee as Self the same as Former Worker Storage?

No. Terminee as Self is self-service for a terminated worker’s own allowed domains. Former Worker Storage is the domain for pre-implementation former-worker records used in rehire.

## Sources checked

-   [Security Group Membership](https://doc.workday.com/workday-education/en-us/course-manuals/security-for-administrators/security-group-membership.html)
-   [FAQ: Terminations](https://doc.workday.com/admin-guide/en-us/human-capital-management/staffing/hire-and-terminate/bwz1497990098885.html)
-   [Concept: Access to Worker Information](https://doc.workday.com/admin-guide/en-us/human-capital-management/worker-information/contact-and-personal-information/contact-information/dan1370797390310.html)
-   [Reference: Security Groups for Pre-Hires](https://doc.workday.com/admin-guide/en-us/human-capital-management/staffing/pre-hire-tracking/ckb1520943781322.html)
-   [Concept: Rehire Former Workers](https://doc.workday.com/admin-guide/en-us/human-capital-management/worker-information/former-workers/dan1385073237213.html)

## Related guides

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

-   [### Separating Production and Sandbox Workday Endpoints So Demos Miss Live Workers Workday gives every tenant its own URL. Production holds live data. Sandbox and Sandbox Preview are typically copies of it. Implementation tenants and the sample-data demonstration tenant are the safer demo targets. A user-delegated connector follows whichever URL the person signs in on.](https://kiweely.com/guides/separate-production-and-sandbox-workday-endpoints)
-   [### Correlating Workday Audit Events with AI Assistant Tool Calls Workday’s agent audit separates the agent account from the person it acted for. Ordinary web-service reads are a weaker trail: Workday does not log GET or unsuccessful web-service requests. A user-delegated connector still acts as the worker, and its own telemetry omits names and pay.](https://kiweely.com/guides/correlating-workday-audit-with-ai-assistant-calls)

### More guides on More Workday guides

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

-   [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)
-   [Building an Open Enrollment Decision Screen on Live Workday Elections](https://kiweely.com/guides/open-enrollment-decision-screen-live-workday-elections)
-   [Mandatory Learning and Acknowledgements with Live Workday Status](https://kiweely.com/guides/mandatory-learning-acknowledgements-live-workday-status)
-   [Day-One Tax, Payment Election, and Form I-9 Pages as Pass-Through](https://kiweely.com/guides/day-one-tax-payment-i9-pass-through-pages)
-   [Compensation Statement Screens and Peer Pay Redaction](https://kiweely.com/guides/compensation-statement-field-redaction-manager-peers)
-   [Publishing One Employee Screen to Web, Teams, and Phone](https://kiweely.com/guides/one-screen-definition-web-teams-phone)

### From the blog on More Workday guides

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

-   [Hiring a Workday FDE: Interview Checklist from Posting Quals](https://kiweely.com/blog/hiring-a-workday-fde-interview-checklist)
-   [Workday FDE Flex Work and Travel: 50% Field Rule and 20% Travel](https://kiweely.com/blog/workday-fde-flex-work-and-travel)
-   [How Workday FDEs Productize Field Insights](https://kiweely.com/blog/workday-fde-product-feedback-loop)

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