Automate employee onboarding, role changes, and offboarding across Microsoft, Google, and Okta
Stepwork reads joiners, movers, and leavers from ADP, Workday, or Rippling, then sets up or removes access in Microsoft 365, Google Workspace, Okta, and every app.
- Use case
- Joiners, movers, and leavers across HR, identity, and every appPeople
- Best for
- IT Manager, People Ops Manager, IT Administrator
- Applications used
Rippling
ADP Workforce Now
Okta
Microsoft Entra ID
Google Workspace
Microsoft Intune
- Business outcome
- Access that matches the HR record, from day one to the last day
The problem
Every hire, move, and exit is a checklist someone runs by hand
- Watch the HR system for new hires, moves, and exits
- Create the account in Entra ID or Google with the right groups
- Work out each department's apps and add them one by one
- Swap groups and app roles when someone changes department
- Close every account, device, and license on the last day
- Show auditors who had access, and when it ended
Triage
Whichever HR system sends it, it lands in the right procedure
Modern HR systems send events. Traditional ones send a report. Managers send a message. Stepwork reads each one where it lands and hands it to the procedure that deals with it.
RipplingWebhook eventevent: employee.terminated worker: Sam Ortiz · Contractor End date: todayGoes to Simple · Leaver in Google Workspace
ADP Workforce NowNightly reportnew_hires_2026-11-16.csv · 6 rows Priya Nair, Store Associate, Retail Daniel Cho, Analyst, FinanceGoes to Microsoft stack · Joiner from ADP
OktaGroup assignmentUser: m.bell@acme.com Added to: dept-sales Apps assigned: 11 · 3 without SCIMGoes to Okta hub · Routing by department
Microsoft TeamsTeams messageHey IT, Dana moves from Support to Engineering on Monday. She'll need production access in AWS.Goes to Mover · Department change with approval
WorkdayTerminationJordan Lee · Senior Engineer Termination: Involuntary · Effective today Manager: K. PatelGoes to Complex · Leaver, end to end
SlackSlack messageAlex starts in Design on the 30th, fully remote. Can someone get the Google account and a MacBook sorted?Goes to Google stack · Joiner from Rippling
- Simple · Leaver in Google WorkspaceFrom
Runs in
Rippling
Google Workspace
Slack
- Microsoft stack · Joiner from ADPFrom
Runs in
ADP Workforce Now
Active Directory
Microsoft Entra ID
Microsoft 365
Microsoft Intune
Microsoft Teams
- Google stack · Joiner from RipplingFrom
Runs in
Rippling
Google Workspace
Internal tool
Jamf
Slack
- Okta hub · Routing by departmentFrom
Runs in
Workday
Okta
Internal tool
Microsoft Teams
- Mover · Department change with approvalFrom
Runs in
Workday
Excel
Microsoft Entra ID
Microsoft Teams
- Complex · Leaver, end to endFrom
Runs in
Workday
Okta
GitHub
Salesforce
Microsoft Intune
Microsoft 365
Systems
The HR systems, identity providers, and suites people get brought into
Your HR system says who joins, moves, and leaves. Your identity provider and your Microsoft or Google suite carry most of the access. Stepwork does the steps between them, and the apps they can't reach, through each app's own screens.
- Traditional HR and payroll: ADP Workforce Now, Paychex Flex, Paylocity
- Modern HR systems: Rippling, Workday, BambooHR, Gusto, Deel
- Identity providers: Okta, Microsoft Entra ID, Active Directory, JumpCloud
- The Microsoft stack: Microsoft 365, Outlook, Microsoft Teams, SharePoint, Microsoft Intune
- The Google stack: Google Workspace, Gmail, Google Drive, Slack, Jamf
- Apps without SCIM: Internal tool, On-prem app, Vendor portal
Example procedures
Six lifecycle procedures, from one rule to end to end
Start with one rule on a modern HR system. Then see the same work on a Microsoft stack fed by a nightly report, a Google stack fed by events, Okta as the hub with routing by department, a mover with an approval gate, and a leaver run end to end. Swap in your own HR system, identity provider, or chat tool above each one.
Suspend a leaver in Google Workspace the moment Rippling records the exit
Rippling
Google Workspace
Slack
Step by step
- The termination arrives as it happensModern HR systems like Rippling send an event when a termination is recorded, so the run starts in seconds, not at the next sync. It carries the leaver's email, their manager, and whether they're an employee or a contractor.
- One rule, two pathsContractors take the top path. Employees take the main lane, because their files need a new owner before the account closes.
- If a contractorSuspend the account in Google Workspace
- If an employeeMove their Drive files to the manager, then suspend
- Contractors are suspendedOnly on the top path: the recorded flow suspends the account in the Google Workspace admin console.Only on this path: If a contractor
- Employees hand over their files firstOn the employee path, Stepwork transfers the leaver's Drive files to their manager, then suspends the account.Only on this path: If an employee
- IT and the manager hear it's doneBoth paths end here. Stepwork posts who was suspended, and where the files went, in Slack.
Field map
| From | To |
|---|---|
New hires from the ADP Workforce Now nightly report into Active Directory, Entra ID, and Microsoft 365
ADP Workforce Now
Active Directory
Microsoft Entra ID
Microsoft 365
Microsoft Intune
Microsoft Teams
Step by step
- The report comes inTraditional HR systems like ADP Workforce Now rarely send events, so Stepwork signs in and reads the new-hire report on a schedule, the same report your team downloads today. Each row is one new hire.
- The account gets createdInside the solid frame, the recorded flow creates the user in Active Directory with the department's OU and groups. Entra ID picks it up on the next sync, so the hybrid setup stays the source of truth.Repeats: For each new hire in the report · 6 hires
- The rule picks the licenseShift, store, and warehouse roles take the top path. Everyone else is an office worker.
- If frontlineAssign a Microsoft 365 F3 license with Teams
- If officeAssign E3, a mailbox, and the department's Teams and SharePoint groups
Repeats: For each new hire in the report · 6 hires - Frontline staff get F3Only on the top path: an F3 license with Teams, so frontline staff get shifts and chat without a full mailbox.Only on this path: If frontlineRepeats: For each new hire in the report · 6 hires
- Office staff get E3 and their groupsOn the office path, Stepwork assigns E3, which creates the Exchange mailbox, and adds the department's Teams and SharePoint groups.Only on this path: If officeRepeats: For each new hire in the report · 6 hires
- A device gets assignedBoth paths rejoin here. Stepwork assigns a device to the new hire in Intune, so it enrolls with their account on first sign-in.Repeats: For each new hire in the report · 6 hires
- The manager hears it's readyThe manager gets the license and device in Microsoft Teams before the start date.
Field map
| From | To |
|---|---|
New hires from Rippling into Google Workspace, Google Groups, and every app on the department's list
Rippling
Google Workspace
Internal tool
Jamf
Slack
Step by step
- The new hire arrives as an eventRippling sends the hire with their department, manager, and start date the moment they're marked ready, so nobody waits for an overnight sync.
- The Google account gets createdThe recorded flow creates the user in the Google Admin console, inside the org unit for their department, so the right policies and apps apply from the start.
- Groups open the shared drivesStepwork adds the new hire to the department's Google Groups. Shared drives, calendars, and mailing lists follow the groups, so there's nothing else to share by hand.
- The app list comes inStepwork reads the department's apps and roles from the sheet your IT team keeps in Google Drive. Each row is one pass through the loop.
- Each app gets the accountInside the solid frame, the recorded flow signs in to each app's admin console and adds the new hire with the role from the sheet, whether or not the app supports SCIM.Repeats: For each app on the department's list · 7 apps
- A Mac gets assignedStepwork assigns a Mac to the new hire in Jamf, so it enrolls with their account on first boot.
- The manager hears it's readyThe manager gets the groups, apps, and device in Slack, with the start date.
Field map
| From | To |
|---|---|
Route each new hire to their department's groups in Okta, then cover the apps it can't push
Workday
Okta
Internal tool
Microsoft Teams
Step by step
- The hire comes in from WorkdayWorkday stays the record of who someone is. The event carries their name, department, and manager.
- Okta gets the profileThe recorded flow creates the user in Okta with the department from Workday on their profile.
- The rule routes by departmentThis is where department logic lives. Engineering, Sales, and Finance each take their own path, and every other team takes the bottom path with the company-wide groups.
- If EngineeringAdd the Engineering groups: GitHub, AWS, Jira
- If SalesAdd the Sales groups: Salesforce, Gong, Outreach
- If FinanceAdd the Finance groups: NetSuite, Ramp
- If any other teamAdd the company-wide groups only
- Engineering gets its groupsOnly for Engineering: the groups that assign GitHub, AWS, and Jira.Only on this path: If Engineering
- Sales gets its groupsOnly for Sales: the groups that assign Salesforce, Gong, and Outreach.Only on this path: If Sales
- Finance gets its groupsOnly for Finance: the groups that assign NetSuite and Ramp.Only on this path: If Finance
- Everyone else gets the basicsEvery other team gets the company-wide groups only. Adding a department later means adding one path to the rule.Only on this path: If any other team
- The paths rejoinEvery path ends here. Stepwork reads the apps the new groups assign in Okta, and whether Okta can push each one.
- The second rule skips what's coveredInside the dashed frame, each app is one pass. Apps Okta pushes through SCIM need nothing more. Apps without SCIM go on to their admin screens.
- If it has no SCIMCreate the account in the app's admin console
- OtherwiseOkta already pushes the account
Repeats: For each app their groups assign · 11 apps - Each remaining app gets the accountThe recorded flow signs in to the app's admin console and adds the new hire, the way an admin would.Only on this path: If it has no SCIMRepeats: For each app their groups assign · 11 apps
- The manager gets the listAfter the last app, the manager gets the groups and accounts in Microsoft Teams.Only on this path: If it has no SCIM
Field map
| From | To |
|---|---|
Swap a mover's access in Microsoft Entra ID when their department changes in Workday
Workday
Excel
Microsoft Entra ID
Microsoft Teams
Step by step
- The move comes inWorkday sends the change with the old and new department and the new manager.
- The old bundle comes inStepwork reads the old department's apps and roles from the bundle sheet your IT team keeps.
- Old access comes off firstThe recorded flow removes the old groups and app roles in Microsoft Entra ID before anything new is granted, so access doesn't pile up with every move.
- The new bundle comes inStepwork reads the new department's apps, and the access level each role carries. Each row is one pass through the loop.
- The rule checks for privileged accessInside the solid frame, admin and production roles take the top path. Standard roles go straight to the grant.
- If privilegedAsk the manager to approve it in Microsoft Teams
- If standardGrant the new group and app role in Microsoft Entra ID
Repeats: For each app in the new bundle · 8 apps - The manager approves privileged rolesOnly on the top path: the manager gets the app and access level in Microsoft Teams, and the grant uses their answer.Only on this path: If privilegedRepeats: For each app in the new bundle · 8 apps
- The new access is grantedBoth paths rejoin here. The recorded flow adds the group or app role in Microsoft Entra ID. A declined approval is noted instead of granted.Repeats: For each app in the new bundle · 8 apps
- The move gets a recordAfter the last app, the Summary card lists what came off, what was granted, and who approved each privileged role.
Field map
| From | To |
|---|---|
Offboard a leaver end to end, by exit type and department
Workday
Okta
GitHub
Salesforce
Microsoft Intune
Microsoft 365
Step by step
- The termination comes inWorkday sends the leaver's email, manager, department, and exit type when the termination is recorded.
- The first rule reads the exit typeSame-day involuntary exits take the top path, contractors the bottom, and planned exits the main lane.
- If same-dayEnd every session in Okta now
- If a contractorClose their client and vendor portal access
- If a planned exitFile handover
- Same-day exits lose access at onceOnly on the top path: every session and token in Okta is ended before anything else runs, so access stops while the rest of the offboarding catches up.Only on this path: If same-day
- Planned exits hand over firstOn the planned path, a nested procedure, the same File handover procedure on the offboarding page, gives the manager the leaver's files while the accounts are still open.Only on this path: If a planned exit
- Contractors lose portal accessOnly for contractors: Stepwork closes the client and vendor portals they were given, which usually sit outside Okta.Only on this path: If a contractor
- The second rule adds department stepsAll three exit paths rejoin here. Engineering, Sales, and Finance each have their own steps. Every other team goes straight to the account.
- If EngineeringRevoke GitHub, AWS keys, and 1Password vaults
- If SalesMove their Salesforce accounts and open deals to the manager
- If FinanceFinance close-out
- If any other teamDeactivate the account in Okta
- Engineering keys get revokedOnly for Engineering: GitHub access, AWS access keys, and shared 1Password vaults are revoked.Only on this path: If Engineering
- Sales records move to the managerOnly for Sales: the leaver's Salesforce accounts and open deals are reassigned to their manager, so no pipeline goes dark.Only on this path: If Sales
- Finance runs its close-outOnly for Finance: another nested procedure suspends cards, moves open expense reports, and flags final pay items.Only on this path: If Finance
- The account is deactivatedEvery path rejoins here. The recorded flow deactivates the account in Okta, which cuts off every app it signs in to.
- The laptop is lockedStepwork locks the device in Microsoft Intune and starts the return, so nothing stays signed in on it.
- Mail and the license are handledThe leaver's mail is forwarded to their manager and the license is freed in Microsoft 365.
- The evidence is writtenThe Summary card lists every step that ran, on which path, and when, so the answer to an access audit is already written.
Field map
| From | To |
|---|---|
Flows
The lifecycle flows these procedures are built from
Each flow is one recorded job in one app. Procedures run them in order for each joiner, mover, or leaver, and any of them can also run on its own from a request.
- Rippling
Extract upcoming new hires
Extracts employees with start dates in the next two weeks, including role, team, and manager. - Rippling
Extract terminations this week
Extracts employees with termination dates this week, including last day and manager. - Rippling
Extract employee directory with departments
Extracts the full employee roster with departments, managers, and employment status. - BambooHR
Extract new hires starting soon
Extracts employees with upcoming start dates, including role, department, and manager. - BambooHR
Extract employee directory changes
Extracts recent role, manager, and department changes from the employee directory. - ADP Workforce Now
Add new hire to payroll
Creates the employee record in ADP with position, compensation, and tax jurisdiction, and initiates onboarding for direct deposit and withholding. - Okta
Create user and assign groups
Creates a new Okta user with name, email, and title, then assigns the group memberships that grant their app entitlements. - Okta
Add user to group
Opens the target Okta group and adds the specified user, granting the app assignments tied to that group. - Okta
Remove user from group
Opens the target Okta group, removes the specified user, and confirms downstream app assignments were revoked. - Okta
Clear active sessions for user
Finds the user in Okta admin and clears all active sessions, forcing re-authentication everywhere. - Okta
Deactivate user account
Signs into the Okta admin console, locates the user by email, deactivates the account, and confirms the status change ended all SSO sessions. - Microsoft Entra ID
Create user with group memberships
Creates a new Entra user and adds them to the security groups that grant team apps and shared resources. - Microsoft Entra ID
Revoke user sessions and tokens
Revokes all active sessions and refresh tokens for a user from the Entra admin center. - Microsoft Entra ID
Disable user account
Signs into the Entra admin center, locates the user, and blocks sign-in, disabling the account across Microsoft services. - Microsoft 365
Assign license to user
Opens the Microsoft 365 admin center, locates the user, and assigns the specified license SKU. - Microsoft 365
Remove license and convert mailbox to shared
Converts a departed user's mailbox to a shared mailbox and removes their paid license in the admin center. - Google Workspace
Create user in org unit
Creates a Google Workspace user with the correct organizational unit and initial password policy applied. - Google Workspace
Transfer Drive ownership to manager
Uses the Google Admin data transfer tool to move a departing user's Drive files to their manager and confirms completion. - Google Workspace
Set departed-user auto-reply and forwarding
Configures email forwarding to a designated inbox and an auto-reply for a departed user's mailbox. - Google Workspace
Suspend user account
Signs into the Google Admin console, locates the user, and suspends the account, blocking sign-in while preserving data. - Microsoft Intune
Retire and wipe device
Issues a retire or wipe action for a departing user's device and confirms the action status. - Internal tool
Swap a mover's role in an app without SCIM
Signs in to the app's admin page, removes the old department's role, adds the new one, and saves the user's page afterwards as a timestamped screenshot.
More procedures
More lifecycle procedures
Ready-made procedures in the Marketplace for new hires, internal moves, contractors, and leavers.
3 more
BambooHR · Okta · Google Workspace + 3 moreNew-hire day-one provisioning
Runs nightly against upcoming start dates in BambooHR, then creates the Okta user with role-based groups, the Google Workspace account in the right org unit with team groups, sends the Slack invite with default channels, provisions Zoom, and invites to the team 1Password vaults, posting a ready-for-day-one summary to IT.- Deel · Okta · Slack
Contractor onboarding with contract issuance
From an approved contractor request, issues the Deel contract, then once countersigned creates a time-boxed Okta account and Slack guest access scoped to the engagement channels. 1 more
Rippling · Okta · Google Workspace + 1 moreSame-day termination deprovision sweep
Extracts this week's terminations from Rippling each morning, cross-checks each against Okta status, and for any still active runs the Okta deactivation, Google Workspace suspension, and Slack deactivation, flagging exceptions to IT.- Freshservice · Jamf
Device recovery and reassignment on departure
Pulls the departing employee's asset assignments from Freshservice, locks the devices in Jamf, and once returned wipes and reassigns them to the next user, updating the asset record trail.
Why Stepwork
One set of rules for every hire, move, and exit, with a record of each
Stepwork is a deterministic agent platform: it runs the steps you recorded in each app, in the same order, every time. Two people in the same department get the same access whether you run Microsoft or Google, ADP or Rippling, and whether an app has SCIM or only an admin screen. Every run records what was granted or removed, on which path, who triggered it, and when. Credentials stay in your vault until a run needs them.
FAQ
Common questions
The math
What manual joiners, movers, and leavers cost IT and People Ops
Example volumes for a company of about 800 people with five hires, three moves, and three exits a week, and about ten apps per department. Swap in yours.
| The manual task | Times a week | Minutes each | Hours a week |
|---|---|---|---|
| Create the account, license, and department groups | 5 | 20 | 1.7 |
| Add a user to an app without SCIM | 30 | 6 | 3 |
| Swap a mover's groups and app roles | 3 | 45 | 2.3 |
| Offboard a leaver across identity, apps, and devices | 3 | 60 | 3 |
| Pull access evidence for an audit request | 2 | 30 | 1 |
- Hours a week
- 11
- Hours a year
- 546
- Of one full-time person
- 27%
