Role-change-to-access records: a sample metadata packet for Workday, Okta and ServiceNow

Short answer

A referral partner can describe a company's role-change-to-access history using only metadata: where the employee event is recorded, how it reaches the identity system, where access requests and removals are ticketed, how long each system keeps its events, and who owns each step. The part worth testing is the mover, someone who changes jobs rather than leaving, because that path is the one most companies never fully automated, and its records show where judgment entered.

Visual briefFull-size diagram
A split panel compares a leaver, whose Workday termination flows through Okta deactivation to a closed ServiceNow ticket, with a mover, whose job change updates Okta groups but leaves a direct app assignment and no revocation record.
Illustrative. The leaver chain closes on its own; the mover chain stops at the first step nobody owns.

The business task: keep access matched to the job

When an employee is hired, moves or leaves, three teams act. HR records the event, the identity team changes what the person can sign in to, and IT fulfills and closes any requests that software cannot handle on its own. The business question is simple to state: on any given day, did each person hold only the access their current job needed, and can the company show who removed the rest?

NIST SP 800-53 frames the same task 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 termination and transfer processes. A company that has worked to that standard tends to have the records a packet describes.

What metadata can a referral partner collect about role-change-to-access without reading private content?

Enough to fill one page per system, without a single name or log line.

Packet fieldWorkday (employee event)Okta (access state)ServiceNow (request and fulfillment)
What is recordedHires, job changes, terminations, effective datesGroup membership, app assignments, System Log eventsAccess requests, approvals, fulfillment tasks
History availableSince the HR system went live90 days in the console; longer only if exportedSince the ticketing tool went live
Where older history livesPrevious HR system, if migratedSIEM or log archive, if anyArchived tables, if any
Join keyEmployee IDEmployee ID attribute, if mappedRequester field, if pulled from the directory
Mover handlingJob change business processGroup rules on department or titleSeparate catalog item, or none
OwnerHR operationsIdentity and access teamIT service management
Unknowns to stateBack-dated changesShare of direct versus group assignmentsWhether removals are ever ticketed

Record counts help too: roughly how many transfers a year, how many applications are provisioned through groups, how many access tickets a month. Approximate is fine. If the company recently changed HR systems, what happens to Workday data after a migration explains which history tends to survive.

The mover test: five questions for the identity owner

The graphic sets a leaver beside a mover (Illustrative). The leaver's termination in Workday deactivates the Okta user and a ServiceNow offboarding ticket closes. The mover's job change moves Okta groups, but an app assigned directly to the person stays, and no removal ticket exists. Ask the identity owner these five questions and record the answers as given:

  1. Is a job change a distinct event in the HR system, with its own effective date? Okta's documentation describes Workday-driven provisioning reflecting updates in Okta, and a move between provisioning groups showing as a group membership change.
  2. Which access follows group rules, and which is assigned to individuals? Group rules can move a user between groups when an attribute such as department changes. Direct assignments do not move with them.
  3. Do directory attributes set at creation stay unchanged? Okta notes that with Workday provisioning the Active Directory OU is set only at creation, so a mover can keep the old one.
  4. Are old-role removals ever ticketed? Many companies ticket requests but not removals, which leaves the last step unrecorded.
  5. How long are identity events kept? Okta keeps System Log events for 90 days; longer history exists only if the company exported or streamed it to a SIEM.

The answers become two packet lines: how many movers a year, and which of the five steps leaves a record. A company that answers "we export the log to our SIEM and run a quarterly transfer review" has a different history from one that answers "the log is what Okta keeps." Both are worth describing.

What stays out of the packet

No user names, no group names that reveal projects, no log extracts, no screenshots of admin consoles, and no description of specific weaknesses. The identity team will rightly refuse those, and an introduction does not need them. If the owner asks whether a buyer would need access to their systems, does a data buyer need access to our systems answers that.

Who sponsors the introduction

Identity records belong to security, HR and IT at once, so the sponsor is whoever can speak for all three: often the CIO or CISO, sometimes the COO. The CEO, often the owner at a mid-size company, is the person who can authorize a licensing discussion. An identity consultant who did the Okta rollout is well placed to describe the systems, but not to authorize anything.

Before you introduce:

  • Confirm 50+ full-time employees at peak, contractors excluded, with a documented operating history.
  • Confirm the company controls these records and that its HR, identity and ticketing contracts do not block licensing.
  • Identify the executive who would take the first call.
  • 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.

Expect a lot to stay open 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 also decide some records are too sensitive to include at all, which is a normal outcome. For the internal side of running such a project, see internal access controls for a sensitive data project; ServiceNow incident data covers the ticketing side, and the systems hub lists other record locations.

Go deeper on role-change-to-access records

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 your client can answer the mover test and name an executive who speaks for HR, identity and IT, register as a partner, confirm who qualifies and review the terms before introducing them.

  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

Are access logs too sensitive to discuss at all?

The logs themselves are sensitive, which is why an introducer never asks for them. Counts, date ranges, retention settings and the name of the identity owner are not. Whether any of it is licensed, and in what form, is decided later under the company's own security review.

Why does the role-change case matter more than terminations?

Most companies automate termination because auditors check it. Transfers are checked less often, so the records show judgment, delay and exceptions. That variety is what makes the history informative, and also what makes gaps likely.

Does SourceX integrate with Okta, Workday or ServiceNow?

No integration is implied. The tools are named because that is where these records commonly sit. A company that proceeds decides what to share under a signed agreement.

Sources

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

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