Skip to content
KiweelyKiweelyKiweely

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
  • Applies to Workday Extend
  • 5 min read
  • Published
  • By Kiweely
On this page
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 (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 separates the groups people confuse in an AI rollout:

Group How membership happens What the constraint is
GroupEmployee as Self, Contingent Worker as Self, Terminee as Self, Retiree as Self How membership happensWorkday-assigned self-service What the constraint isThat person’s own data
GroupAll Employees, All Contingent Workers, All Retirees, All Terminees How membership happensWorkday-assigned public groups What the constraint isPublic data, not every private field
GroupHR Partner and other role-based groups How membership happensDerived from a role on a position or job What the constraint isTarget data in the organizations where the role is assigned

Security groups for pre-hires 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 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 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 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. 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

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.