Role-change-to-access record chain: how the employee ID joins Workday, Okta and ServiceNow for one transfer

Short answer

A company connects role-change-to-access records through the employee ID: issued by the HR system, mapped onto the identity profile, and pulled into every access ticket through the requester field. The join is strong where each system reads the ID from the one before it, and weak where people type names. For someone who changes jobs rather than leaving, the weakest link is the last one: proof that access tied to the old role was removed, which often has no record at all.

Visual briefFull-size diagram
A vertical chain of records for one transfer, Workday job change, Okta group move, ServiceNow access request and fulfilled ticket, clicks together on the employee ID; a final link for removing the old payables app is highlighted as missing, then repaired by a group-based assignment and a removal ticket.
Illustrative transfer at a fictional logistics company. The chain grants new access cleanly; the removal link holds only when someone builds it.

This page is part of the role-change-to-access records guide, which covers the metadata packet and the mover test. Here the focus is the chain itself: which identifier joins each step, where it breaks and how companies repair it.

The spine: one immutable employee ID

Every link in this chain depends on one value surviving three systems. HR issues an employee ID at hire. The sign-on platform stores it on the person's profile, ideally filled in automatically from the HR feed. The ticketing tool then needs that same person as the requester or subject of each access ticket, which works when the form looks the person up instead of accepting a typed name.

Okta's documentation describes the first half for a Workday feed: HR updates flow through to Okta and downstream apps, and a worker placed in a different HR group shows up as a changed Okta group. Group rules can then shift a user between groups when a field such as department changes. Those two features make the first hops of the chain largely automatic. The later hops are not.

The chain for one transfer (Illustrative)

A fictional 650-person logistics company. An analyst moves from accounts payable to sales operations, effective March 3. Every value is invented to show how the key carries.

StepDateSystemRecordJoin keyStatus
1Feb 20WorkdayJob change entered, effective March 3Employee IDRecorded
2Mar 3OktaDepartment field updates; group rule moves the user from Finance to Sales groupsEmployee ID on the profileRecorded
3Mar 4ServiceNowRequest for CRM access opened by the new managerRequester looked up, not typedRecorded
4Mar 6ServiceNowCRM access fulfilled and ticket closedSame ticketRecorded
5NoneServiceNowNo ticket to remove the payables application, which was assigned directlyNoneMissing
6Jun 1OktaSystem Log events from early March pass the 90-day markNot applicableLost unless exported

Steps 1 to 4 join cleanly, because each record reads the employee ID from the system before it. Step 5 is the case that usually goes unresolved: a user who changes roles rather than leaving. Nothing in the job change asked anyone to remove the payables app, so no record exists to carry the key. Step 6 is a retention fact rather than a process failure: identity events in Okta are kept for 90 days unless exported or streamed elsewhere.

Where the chain breaks for a transferee

Leavers are usually handled end to end, because a termination shuts the account. Someone who changes jobs keeps the account, so every removal has to be specific. Four breaks recur:

  1. Direct assignments do not follow group rules. Apps assigned to a person rather than a group stay when the department changes. Step 5 above is this break.
  2. Values set only at creation stay behind. Okta notes that with a Workday feed the Active Directory OU is set only when the user is created, so a transferee can keep the old OU and whatever depends on it.
  3. Typed names on tickets. If the access form accepts free text, a ticket can name "J. Smith" without the employee ID, and the join becomes a guess.
  4. Identity events age out. Without export, the identity system cannot show in 2027 what changed in early 2026. The HR and ticket records survive; the evidence that access actually changed may not.

NIST SP 800-53 describes why this matters as a control: its personnel transfer control asks organizations to review and confirm ongoing need for access when someone is reassigned and to modify authorizations to match, and its account management control asks that accounts follow transfer processes. A company working to that standard is more likely to have built the last link.

Companies that close the transfer gap tend to use some combination of four fixes, and the year each began sets where the reliable history starts:

  • Move direct assignments into groups, so a group rule on department removes old-role apps automatically and the identity log records it.
  • Open a removal task on every job change, created from the HR event and closed by the app owner, so the ticket system holds a record for step 5.
  • Require directory lookup on access forms, so every ticket carries the employee ID rather than a typed name.
  • Stream identity logs to a SIEM or archive, so the 90-day window stops being the edge of the evidence.

The graphic on this page shows the first two: the missing removal link turns green once the payables app is group-based and a removal ticket exists. Ask which fixes the company uses and since when; ServiceNow data archiving and retention explains how long ticket history usually survives once it is in place.

What a partner records about linkage, and who can authorize it

Describe the chain without touching it. Five notes cover it: which identifier is the spine and whether all three systems store it; whether access forms look the person up or accept typed names; roughly what share of access is group-based versus directly assigned; whether removals on transfer are ticketed; and where identity logs go after 90 days. No user names, group names, log lines or console screenshots.

Identity records belong to HR, security and IT at once, so the sponsor is whoever can speak for all three, often the CIO or CISO, or the COO at a mid-size company. The CEO authorizes any licensing discussion. Before you introduce, confirm 50+ full-time employees at peak (contractors excluded), documented operating history, rights to license and an authorized contact. Companies in the U.S., Canada and the EU qualify, as do companies in the UK, Australia, New Zealand, India, Singapore, South Africa, Latin America, the UAE and Saudi Arabia when at least 70% of the data is in English.

What stays unknown until SourceX reviews it: what must be excluded for security reasons, how employee data is de-identified, which periods a buyer would value and what the company would be paid. The company may decide some records are too sensitive to include, which is a normal outcome; who has access to data in a licensing deal answers the usual first worry. If HR history moved systems recently, see Workday data export after migration; for the ticketing side, see ServiceNow incident data. To mark the trail pass, partial or fail, use the companion role-change-to-access completeness checklist.

Next step

Refer a company. No cap on rewards. Default reward on a company's first qualifying transaction: the greater of $50,000 plus 5% and 15% of Actual Supplier Payout, with no cap; further qualifying transactions first agreed within 12 months of the first Closing pay 15%. Eligibility and payment conditions apply, including the USD 100,000 Minimum Transaction, and a signed Schedule A or addendum can differ. A lead, meeting or signature alone does not trigger payment.

If the identity owner can name the spine identifier and say whether removals on transfer leave a record, register as a partner, confirm the company on who qualifies and read the program terms before you introduce the sponsor.

  1. Step 1Share your linkSend your personal link to a company you know.
  2. Step 2Company appliesThe company applies itself at /apply.
  3. Step 3Company signs and is paidThe company signs, delivers its data and is paid by SourceX under its agreement.
  4. Step 4You get your rewardthe greater of $50,000 plus 5% and 15% of the actual supplier payout, with no cap. A reward becomes payable after SourceX has paid the referred company under its signed agreement and the payout conditions in the program terms are met, including finance approval and your tax and payment details.

Common questions

What if the company uses a different HR, identity or ticketing tool?

The chain is the same: an HR event, an identity change and a ticket. Ask which identifier the HR system issues and whether the identity and ticketing tools store it. The tools named here are examples, and no SourceX connector is implied.

Is a name or email address good enough as a join key?

It works for a person reading one case. Across years it fails: people change names, emails are reused and two employees can share a name. An immutable employee ID carried into every system is what makes the chain hold.

Do I need to see any log lines to describe the linkage?

No. The identity owner can tell you which attribute holds the employee ID, how the ticketing form picks the requester and where logs go after 90 days. That is the whole description an introduction needs.

Sources

  1. help.okta.com/en-us/content/topics/provisioning/workday/wo…
  2. help.okta.com/en-us/content/topics/users-groups-profiles/u…
  3. support.okta.com/help/s/article/Exporting-Okta-Log-Data
  4. nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-53r…
  5. refer.sourcex.si/terms

Free resources

Know a company with valuable proprietary data?

Become a referral partner, get your link and introduce the company’s CEO (in an owner-run company, usually the owner). Referral partners can join from most countries. We can't work with partners in countries or regions under U.S. sanctions or on U.S. restricted-party lists. The companies you introduce should be based in the U.S., Canada and the EU, or in the UK, Australia, New Zealand, India, Singapore, South Africa, Latin America, the UAE and Saudi Arabia with at least 70% of their data in English.

Refer a company →

I own a business

Explore licensing your company's data directly to SourceX for AI training and evaluation. Start a short assessment; no uploads needed.

Start an assessment