This page reads one transfer twice, first as the request log alone and then with its surrounding records. It is part of the role-change-to-access records guide, which covers the full metadata packet.
Before: one transfer as the ServiceNow request log tells it
The case is Illustrative, built for this page. A fictional 620-person regional insurer moves a claims analyst into an underwriting assistant role. Here is everything a ServiceNow-only export holds about that move.
| Ticket | Opened | Item requested | Justification field | Approver | State |
|---|---|---|---|---|---|
| Request 1 | Day 2 | Underwriting workbench | "New role" | Underwriting manager | Closed, fulfilled |
| Request 2 | Day 2 | Rating tool, read and write | Blank | Underwriting manager | Closed, fulfilled |
| Request 3 | Day 9 | Underwriting shared drive | "Needed for referrals" | Team lead | Closed, fulfilled |
A reader of this export learns that three requests were raised and fulfilled. It cannot tell from the log that this person had changed jobs; two of the three justifications say almost nothing. It cannot tell whether the person was entitled to the rating tool on day 2, because the export holds the approver's name, not the requester's role. And it holds no trace of the claims system the analyst used for four years, because nobody raised a ticket to remove it.
That last absence is the trap. An empty removal history looks the same whether the removal happened automatically, happened informally, or never happened at all.
After: the same transfer with Workday and Okta beside it
Put the HR event and the identity changes next to those three tickets and the story changes.
| When | System | What the record shows |
|---|---|---|
| Day 0 | Workday | Job change, claims analyst to underwriting assistant, department changed, effective date recorded |
| Day 1 | Okta | Department attribute updated from the HR feed; a group rule moves the user from the claims group to the underwriting group |
| Day 1 | Okta | Claims reporting app, granted through the claims group, removed with the group change |
| Day 2 | ServiceNow | Requests 1 and 2 raised and fulfilled |
| Day 9 | ServiceNow | Request 3 raised and fulfilled |
| Day 1 to 47 | Okta | Claims system, assigned to the person directly years earlier, still assigned |
| Day 47 | Okta | Direct assignment removed after a quarterly access review flagged a role mismatch |
Now the record says something a buyer could learn from. The organization automated the part of the move that ran through groups, which Okta's documentation describes: group rules can move a user between groups when a profile attribute such as department changes. The part assigned to the individual did not follow the person, and it took a review 47 days later to catch it. NIST SP 800-53 control PS-5 expects exactly that review when someone is reassigned, so the joined record also shows when the company's practice met the standard and when it lagged.
What the gap hides, and which system holds it
Each row is context the request log drops on its own, and the system where it usually lives instead. "Usually" matters: some companies keep more in ServiceNow, others less.
| Lost without context | ServiceNow export alone | Where the context usually lives |
|---|---|---|
| Why the access was requested | Free-text justification, often blank | Workday job change, with effective date |
| Whether the requester was entitled | Approver's name only | Workday role and department on the request date |
| What was granted automatically | Nothing; only ticketed grants appear | Okta group rule changes |
| Whether old access was removed | Absent unless someone ticketed a removal | Okta group removals; direct assignments flagged separately |
| How long the mismatch lasted | Unknown | Days between the Workday effective date and the Okta removal |
| Which removals were caught by review | Unknown | Access review records, wherever the company keeps them |
| Directory attributes left from the old role | Unknown | Active Directory, where Okta's Workday guide notes the OU is set only at creation |
The right-hand column is where the training value sits: a labeled history of an organization deciding who should hold what, including where it got that wrong and how long correction took. The middle column is a request log. Both are real records, but they answer different questions, and an introduction should not describe one as the other. The broader pattern of records that look complete while missing their reasons is covered in what data is missing from AI training.
The access nobody asked to remove
Leavers rarely produce this gap. A termination in the HR system usually deactivates the identity account in one step, and every app goes with it. A mover is a grant plus a removal, and only the grant is somebody's job: the new manager wants the new tools working, while nobody is measured on the old ones disappearing.
Three facts decide how much of the mover's story survives, and each can be asked about without seeing a record:
- Share of access granted through groups. Group-based access follows the person when the department attribute changes. Direct assignments stay until someone acts. Ask the identity owner for a rough share.
- Identity log retention. Okta keeps System Log events for 90 days. Unless the company exported the log or streamed it to a SIEM, the day-1 and day-47 rows above vanish after three months, leaving only the HR event and the tickets.
- Whether reviews leave a record. A quarterly access review that ends in a spreadsheet signed off by email leaves a different trace from one recorded as tickets. Either is fine to describe; just say which.
If the company archives older ServiceNow tables, the ServiceNow archiving and retention guide explains what tends to stay queryable, and ServiceNow incident data covers the ticket side more broadly. The keys that make the joined view possible, such as the employee ID carried into Okta and into the ServiceNow requester field, are the subject of the companion page on linking HR, identity and ticket records.
Describing the missing context without moving any records
You do not need the export, the log or a single name to describe this. You need four answers from the identity owner, recorded as given:
- Which systems hold the job change, the group and assignment changes, and the access tickets, and since when?
- Roughly how many transfers happen in a year?
- Is the identity log kept beyond the platform default, and where?
- Is there any report of access that outlived a role change?
Partners never ask for or handle raw client records. Discovery stays at metadata level: what exists, how much, how long, which system, and who owns it. If the identity team worries that a buyer would need to log in to their systems, does a data buyer need access to our systems answers that for them.
The records belong to HR, security and IT at once, so the person who can authorize a licensing discussion is the CEO, or the owner-CEO in an owner-run company, not the Okta administrator who knows the setup best; the CIO or CISO often sponsors it. Before introducing, confirm 50+ full-time employees at peak (contractors excluded), a 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. Sign the Channel Partner Agreement first.
What stays unknown until SourceX reviews it: whether employee data can be de-identified to a buyer's standard, which security details must be excluded, whether any buyer wants this record type, and what the company would be paid. The completeness checklist adds a pass, partial or fail score if you want to go further. Naming Okta, Workday and ServiceNow here describes where records commonly sit; it does not imply a SourceX connector. Other record locations are listed under systems.
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 company can say where each piece of a transfer's context lives and an executive will speak for HR, identity and IT together, register as a partner, check who qualifies, and read the terms before you introduce them.