People Systems Interoperability
Recover and control
worked transaction
The record did not arrive: recover an employment integration change without duplicating it
An approved change in one system is evidence of approval there. It is not proof that the receiving system has it. When a leave request is missing, the immediate job is to establish the last verified state, give one owner control of recovery, and confirm the final record before anyone sends the chang
Read article ↗LISTICLEEORs for teams using a separate identity system for employee access
Your People team confirms that a UK employee has left. IT still needs the right employee ID, the effective time and an instruction it can act on before it removes access in Okta. If the EOR says “offboarded” while the account remains live, the gap is yours to find. A longer integration list will not
Read article ↗GUIDESeparate integration access from employment approval
Define who may change each record and who approves the employment decision.
Open guide ↗GUIDEOne employee, two identifiers: prevent duplicate employment records
The decision: establish an approved match between the client’s employee record and the provider’s record before synchronising employment changes. A name match is a search clue, not permission to update a record. If the match is wrong, a change meant for one worker can land on another worker’s employ
Read article ↗GUIDEConnect an existing team without changing every record at once
Decision: use a phased cutover when you can isolate cohorts and reconcile each one before releasing the next. For the fictional twelve-person team below, activate four people first and hold the remaining eight. The first cohort exposes a leave-policy mismatch: one corrected request is right in the e
Read article ↗GUIDEWho may change what? Separate integration access from employment approval
A connector credential answers who can move data. It does not answer who authorised a change to someone’s employment terms. For a salary change, give the integration account only the access needed to carry a decision that has already been made and reviewed. If the connector cannot distinguish an app
Read article ↗