Skip to content
Stepwork logoStepwork logo
Marketplace
Deterministic AgentsSecurity

The Stepwork Platform

Deterministic work across the tools you already run

  • Extraction
  • Rule
  • Webhook

In product

  • ProcedureRun the process end to end
  • ExtractionPull data into the next step
  • Ask BobBuild a flow by chatting

Solutions

How Stepwork shows up for your team and industry

By team

  • ITAccounts, access, helpdesk requests
  • Security & ComplianceAccess reviews, evidence, audits
  • Finance & AccountingInvoices, billing, month-end close
  • Sales & RevOpsCRM to ERP, orders, quotes
  • OperationsOrders, deliveries, dispatch
  • HR & PeopleOnboarding and offboarding
See all teams

By industry

  • HealthcareReferrals, eligibility checks, EHR entry
  • 3PL and warehousingPDF orders, WMS entry, client billing
  • Freight and truckingRate confirmations, carrier checks, TMS
  • Fuel and convenience storesStore staff, POS IDs, back office
  • ConstructionJob setup, subcontractor insurance
  • Manufacturing and distributionPO entry, supplier dates, legacy ERPs
  • Accounting firmsMonth-end across every client file
  • Field services and tradesService calls to jobs to invoices
  • MSPsNew users and license true-ups
See all industries
Log inBook a Demo

Product

  • ProcedureRun the process end to end
  • ExtractionPull data into the next step
  • Ask BobBuild a flow by chatting
Marketplace

By team

  • ITAccounts, access, helpdesk requests
  • Security & ComplianceAccess reviews, evidence, audits
  • Finance & AccountingInvoices, billing, month-end close
  • Sales & RevOpsCRM to ERP, orders, quotes
  • OperationsOrders, deliveries, dispatch
  • HR & PeopleOnboarding and offboarding
See all teams

By industry

  • HealthcareReferrals, eligibility checks, EHR entry
  • 3PL and warehousingPDF orders, WMS entry, client billing
  • Freight and truckingRate confirmations, carrier checks, TMS
  • Fuel and convenience storesStore staff, POS IDs, back office
  • ConstructionJob setup, subcontractor insurance
  • Manufacturing and distributionPO entry, supplier dates, legacy ERPs
  • Accounting firmsMonth-end across every client file
  • Field services and tradesService calls to jobs to invoices
  • MSPsNew users and license true-ups
See all industries
Deterministic AgentsSecurity
Log inBook a Demo
  1. Home
  2. Solutions
  3. Employee lifecycle automation

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.

Book a DemoSee the procedures
  • New hire webhook
  • Nightly HR report
  • Department change
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
  • Triage
  • Systems
  • Example procedures
  • Flows
  • More procedures
  • Why Stepwork
  • Related use cases
  • FAQ
  • The math

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.

How it arrives
  • RipplingWebhook eventevent: employee.terminated worker: Sam Ortiz · Contractor End date: todaySGoes 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, FinanceMGoes to Microsoft stack · Joiner from ADP
  • OktaGroup assignmentUser: m.bell@acme.com Added to: dept-sales Apps assigned: 11 · 3 without SCIMOGoes 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.VGoes to Mover · Department change with approval
  • WorkdayTerminationJordan Lee · Senior Engineer Termination: Involuntary · Effective today Manager: K. PatelLGoes 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?GGoes to Google stack · Joiner from Rippling
Where it goes
  • SSimple · Leaver in Google WorkspaceFromRuns inRipplingGoogle WorkspaceSlack
  • MMicrosoft stack · Joiner from ADPFromRuns inADP Workforce NowActive DirectoryMicrosoft Entra IDMicrosoft 365Microsoft IntuneMicrosoft Teams
  • GGoogle stack · Joiner from RipplingFromRuns inRipplingGoogle WorkspaceInternal toolJamfSlack
  • OOkta hub · Routing by departmentFromRuns inWorkdayOktaInternal toolMicrosoft Teams
  • VMover · Department change with approvalFromRuns inWorkdayExcelMicrosoft Entra IDMicrosoft Teams
  • LComplex · Leaver, end to endFromRuns inWorkdayOktaGitHubSalesforceMicrosoft IntuneMicrosoft 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
  • ADP Workforce Now
  • Paychex Flex
  • Paylocity
  • Rippling
  • BambooHR
  • Gusto
  • Deel
  • ADP Workforce Now
  • Paychex Flex
  • Paylocity
  • Rippling
  • BambooHR
  • Gusto
  • Deel
  • ADP Workforce Now
  • Paychex Flex
  • Paylocity
  • Rippling
  • BambooHR
  • Gusto
  • Deel
  • ADP Workforce Now
  • Paychex Flex
  • Paylocity
  • Rippling
  • BambooHR
  • Gusto
  • Deel
  • Microsoft Entra ID
  • Active Directory
  • JumpCloud
  • Outlook
  • Microsoft Teams
  • SharePoint
  • Microsoft Intune
  • Microsoft Entra ID
  • Active Directory
  • JumpCloud
  • Outlook
  • Microsoft Teams
  • SharePoint
  • Microsoft Intune
  • Microsoft Entra ID
  • Active Directory
  • JumpCloud
  • Outlook
  • Microsoft Teams
  • SharePoint
  • Microsoft Intune
  • Microsoft Entra ID
  • Active Directory
  • JumpCloud
  • Outlook
  • Microsoft Teams
  • SharePoint
  • Microsoft Intune
  • Gmail
  • Google Drive
  • Jamf
  • Internal tool
  • On-prem app
  • Vendor portal
  • Gmail
  • Google Drive
  • Jamf
  • Internal tool
  • On-prem app
  • Vendor portal
  • Gmail
  • Google Drive
  • Jamf
  • Internal tool
  • On-prem app
  • Vendor portal
  • Gmail
  • Google Drive
  • Jamf
  • Internal tool
  • On-prem app
  • Vendor portal
  • Gmail
  • Google Drive
  • Jamf
  • Internal tool
  • On-prem app
  • Vendor portal
  • Gmail
  • Google Drive
  • Jamf
  • 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

The simplest version: Rippling sends a webhook the moment a termination is recorded, one rule checks whether the leaver is a contractor, and the account is suspended in Google Workspace. Employees' Drive files go to their manager first.
  • Rippling
  • Google Workspace
  • Slack
Swap in your systemsThe steps stay the same. Only the screens change.
HR system
Team chat
Suspend a leaver in Google Workspace the moment Rippling records the exit
Webhook
Rippling

Termination recorded in Rippling

webhook · employee terminated

Output variables

  • employee_email
  • manager_email
  • worker_type
Rule logic

Is it a contractor?

Input variables

  • worker_type

Paths

  1. If Rippling lists them as a contractor, not an employeeThen: Suspend the account in Google Workspace
  2. OtherwiseThen: Move their Drive files to the manager, then suspend
Execution
If a contractor
Google Workspace

Suspend the account in Google Workspace

Input variables

  • employee_email

Output

  • suspended
Execution
If an employee
Google Workspace

Move their Drive files to the manager, then suspend

Input variables

  • employee_email
  • manager_email

Output

  • suspended
Execution
Slack

Post the offboarding in Slack

Input variables

  • manager_email
  • suspended

Drag to explore · pinch to zoom

Step by step

  1. 1
    The termination arrives as it happens
    Modern 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.
  2. 2
    One rule, two paths
    Contractors 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
  3. 3
    Contractors are suspended
    Only on the top path: the recorded flow suspends the account in the Google Workspace admin console.
    Only on this path: If a contractor
  4. 4
    Employees hand over their files first
    On the employee path, Stepwork transfers the leaver's Drive files to their manager, then suspends the account.
    Only on this path: If an employee
  5. 5
    IT and the manager hear it's done
    Both paths end here. Stepwork posts who was suspended, and where the files went, in Slack.

Field map

FromTo
RipplingTermination: work emailGoogle WorkspaceUser: suspend
RipplingManager emailGoogle WorkspaceDrive transfer: new ownerEmployees only

New hires from the ADP Workforce Now nightly report into Active Directory, Entra ID, and Microsoft 365

Every weekday morning Stepwork reads the new-hire report from ADP Workforce Now, creates each hire in Active Directory so they sync to Entra ID, and picks the Microsoft 365 license by role. Frontline staff get F3, office staff get E3 with a mailbox and their department's Teams and SharePoint groups. Intune gets a device ready and the manager hears what works.
  • ADP Workforce Now
  • Active Directory
  • Microsoft Entra ID
  • Microsoft 365
  • Microsoft Intune
  • Microsoft Teams
Swap in your systemsThe steps stay the same. Only the screens change.
HR system
Team chat

Step by step

  1. 1
    The report comes in
    Traditional 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.
  2. 2
    The account gets created
    Inside 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
  3. 3
    The rule picks the license
    Shift, 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
  4. 4
    Frontline staff get F3
    Only 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
  5. 5
    Office staff get E3 and their groups
    On 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
  6. 6
    A device gets assigned
    Both 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
  7. 7
    The manager hears it's ready
    The manager gets the license and device in Microsoft Teams before the start date.

Field map

FromTo
ADP Workforce NowNew hire report: name, departmentActive DirectoryNew user: name, OU, groups
ADP Workforce NowJob typeMicrosoft 365License: F3 or E3
Microsoft Entra IDUser principal nameMicrosoft IntuneDevice: assigned user

New hires from Rippling into Google Workspace, Google Groups, and every app on the department's list

When Rippling marks a new hire ready, Stepwork creates their Google account in the department's org unit, adds the Google Groups that open the right shared drives and calendars, adds them in every app on the department's list, and assigns a Mac in Jamf. The manager hears what's ready.
  • Rippling
  • Google Workspace
  • Internal tool
  • Jamf
  • Slack
Swap in your systemsThe steps stay the same. Only the screens change.
HR system
Team chat

Step by step

  1. 1
    The new hire arrives as an event
    Rippling sends the hire with their department, manager, and start date the moment they're marked ready, so nobody waits for an overnight sync.
  2. 2
    The Google account gets created
    The 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.
  3. 3
    Groups open the shared drives
    Stepwork 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.
  4. 4
    The app list comes in
    Stepwork 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.
  5. 5
    Each app gets the account
    Inside 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
  6. 6
    A Mac gets assigned
    Stepwork assigns a Mac to the new hire in Jamf, so it enrolls with their account on first boot.
  7. 7
    The manager hears it's ready
    The manager gets the groups, apps, and device in Slack, with the start date.

Field map

FromTo
RipplingNew hire: name, departmentGoogle WorkspaceNew user: name, org unit
RipplingDepartmentGoogle WorkspaceGroup memberships
Google WorkspacePrimary emailJamfDevice: assigned user

Route each new hire to their department's groups in Okta, then cover the apps it can't push

When Workday creates a hire, Stepwork creates their profile in Okta and a rule routes them to their department's groups: Engineering, Sales, Finance, or the company-wide set. Okta pushes every app it can through SCIM, and a second rule sends the rest through their own admin screens.
  • Workday
  • Okta
  • Internal tool
  • Microsoft Teams
Swap in your systemsThe steps stay the same. Only the screens change.
HR system
Identity provider
Team chat

Step by step

  1. 1
    The hire comes in from Workday
    Workday stays the record of who someone is. The event carries their name, department, and manager.
  2. 2
    Okta gets the profile
    The recorded flow creates the user in Okta with the department from Workday on their profile.
  3. 3
    The rule routes by department
    This 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
  4. 4
    Engineering gets its groups
    Only for Engineering: the groups that assign GitHub, AWS, and Jira.
    Only on this path: If Engineering
  5. 5
    Sales gets its groups
    Only for Sales: the groups that assign Salesforce, Gong, and Outreach.
    Only on this path: If Sales
  6. 6
    Finance gets its groups
    Only for Finance: the groups that assign NetSuite and Ramp.
    Only on this path: If Finance
  7. 7
    Everyone else gets the basics
    Every 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
  8. 8
    The paths rejoin
    Every path ends here. Stepwork reads the apps the new groups assign in Okta, and whether Okta can push each one.
  9. 9
    The second rule skips what's covered
    Inside 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
  10. 10
    Each remaining app gets the account
    The 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
  11. 11
    The manager gets the list
    After the last app, the manager gets the groups and accounts in Microsoft Teams.
    Only on this path: If it has no SCIM

Field map

FromTo
WorkdayWorker: name, departmentOktaProfile: name, department
WorkdayDepartmentOktaGroup membershipsPicked by the department rule
OktaWork emailInternal toolAdd user: emailOnly apps without SCIM

Swap a mover's access in Microsoft Entra ID when their department changes in Workday

When a department change takes effect in Workday, Stepwork removes the old department's groups and app roles in Microsoft Entra ID, then grants each app in the new bundle. Privileged roles go to the manager for approval in Microsoft Teams before they're granted, so movers don't keep old access or get admin rights unseen.
  • Workday
  • Excel
  • Microsoft Entra ID
  • Microsoft Teams
Swap in your systemsThe steps stay the same. Only the screens change.
HR system
Identity provider
Team chat

Step by step

  1. 1
    The move comes in
    Workday sends the change with the old and new department and the new manager.
  2. 2
    The old bundle comes in
    Stepwork reads the old department's apps and roles from the bundle sheet your IT team keeps.
  3. 3
    Old access comes off first
    The 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.
  4. 4
    The new bundle comes in
    Stepwork reads the new department's apps, and the access level each role carries. Each row is one pass through the loop.
  5. 5
    The rule checks for privileged access
    Inside 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
  6. 6
    The manager approves privileged roles
    Only 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
  7. 7
    The new access is granted
    Both 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
  8. 8
    The move gets a record
    After the last app, the Summary card lists what came off, what was granted, and who approved each privileged role.

Field map

FromTo
WorkdayOld departmentMicrosoft Entra IDGroups to remove
ExcelNew bundle: app and access levelMicrosoft Entra IDGroups to add
Microsoft TeamsManager's approvalMicrosoft Entra IDPrivileged role grantPrivileged roles only

Offboard a leaver end to end, by exit type and department

The full version. A termination in Workday goes through two rules: one for the kind of exit, one for the department. Same-day exits lose every session at once, contractors lose portal access, and planned exits hand over their files through a nested procedure. Each department's own steps run next, then Okta, Microsoft Intune, and Microsoft 365 close in order and the run writes the evidence an auditor asks for.
  • Workday
  • Okta
  • GitHub
  • Salesforce
  • Microsoft Intune
  • Microsoft 365
Swap in your systemsThe steps stay the same. Only the screens change.
HR system
Identity provider
Device management
Workspace

Step by step

  1. 1
    The termination comes in
    Workday sends the leaver's email, manager, department, and exit type when the termination is recorded.
  2. 2
    The first rule reads the exit type
    Same-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
  3. 3
    Same-day exits lose access at once
    Only 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
  4. 4
    Planned exits hand over first
    On 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
  5. 5
    Contractors lose portal access
    Only for contractors: Stepwork closes the client and vendor portals they were given, which usually sit outside Okta.
    Only on this path: If a contractor
  6. 6
    The second rule adds department steps
    All 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
  7. 7
    Engineering keys get revoked
    Only for Engineering: GitHub access, AWS access keys, and shared 1Password vaults are revoked.
    Only on this path: If Engineering
  8. 8
    Sales records move to the manager
    Only 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
  9. 9
    Finance runs its close-out
    Only for Finance: another nested procedure suspends cards, moves open expense reports, and flags final pay items.
    Only on this path: If Finance
  10. 10
    The account is deactivated
    Every path rejoins here. The recorded flow deactivates the account in Okta, which cuts off every app it signs in to.
  11. 11
    The laptop is locked
    Stepwork locks the device in Microsoft Intune and starts the return, so nothing stays signed in on it.
  12. 12
    Mail and the license are handled
    The leaver's mail is forwarded to their manager and the license is freed in Microsoft 365.
  13. 13
    The evidence is written
    The Summary card lists every step that ran, on which path, and when, so the answer to an access audit is already written.

Field map

FromTo
WorkdayTermination: exit type, departmentOktaWhich paths runRead by both rules
WorkdayManager emailSalesforceAccount and opportunity ownerSales only
WorkdayManager emailMicrosoft 365Mail forwarding: recipient

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
    Rippling

    Extract upcoming new hires

    Extracts employees with start dates in the next two weeks, including role, team, and manager.

    Extraction · Scheduled
  • Rippling
    Rippling

    Extract terminations this week

    Extracts employees with termination dates this week, including last day and manager.

    Extraction · Scheduled
  • Rippling
    Rippling

    Extract employee directory with departments

    Extracts the full employee roster with departments, managers, and employment status.

    Extraction · Scheduled
  • BambooHR
    BambooHR

    Extract new hires starting soon

    Extracts employees with upcoming start dates, including role, department, and manager.

    Extraction · Scheduled
  • BambooHR
    BambooHR

    Extract employee directory changes

    Extracts recent role, manager, and department changes from the employee directory.

    Extraction · Scheduled
  • ADP Workforce Now
    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.

    Execution · Slack request
  • Okta
    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.

    Execution · Slack request
  • Okta
    Okta

    Add user to group

    Opens the target Okta group and adds the specified user, granting the app assignments tied to that group.

    Execution · Slack request
  • Okta
    Okta

    Remove user from group

    Opens the target Okta group, removes the specified user, and confirms downstream app assignments were revoked.

    Execution · Slack request
  • Okta
    Okta

    Clear active sessions for user

    Finds the user in Okta admin and clears all active sessions, forcing re-authentication everywhere.

    Execution · Slack request
  • Okta
    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.

    Execution · Slack request
  • Microsoft Entra ID
    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.

    Execution · Slack request
  • Microsoft Entra ID
    Microsoft Entra ID

    Revoke user sessions and tokens

    Revokes all active sessions and refresh tokens for a user from the Entra admin center.

    Execution · Slack request
  • Microsoft Entra ID
    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.

    Execution · Slack request
  • Microsoft 365
    Microsoft 365

    Assign license to user

    Opens the Microsoft 365 admin center, locates the user, and assigns the specified license SKU.

    Execution · Slack request
  • Microsoft 365
    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.

    Execution · Slack request
  • Google Workspace
    Google Workspace

    Create user in org unit

    Creates a Google Workspace user with the correct organizational unit and initial password policy applied.

    Execution · Slack request
  • Google Workspace
    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.

    Execution · Slack request
  • Google Workspace
    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.

    Execution · Slack request
  • Google Workspace
    Google Workspace

    Suspend user account

    Signs into the Google Admin console, locates the user, and suspends the account, blocking sign-in while preserving data.

    Execution · Slack request
  • Microsoft Intune
    Microsoft Intune

    Retire and wipe device

    Issues a retire or wipe action for a departing user's device and confirms the action status.

    Execution · Slack request
  • Internal tool
    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.

    Recorded on your screens
See every employee onboarding flow in the Marketplace

More procedures

More lifecycle procedures

Ready-made procedures in the Marketplace for new hires, internal moves, contractors, and leavers.

  • BambooHROktaGoogle Workspace3 more
    BambooHR · Okta · Google Workspace + 3 more

    New-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.
  • DeelOktaSlack
    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.
  • RipplingOktaGoogle Workspace1 more
    Rippling · Okta · Google Workspace + 1 more

    Same-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.
  • FreshserviceJamf
    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.

Deterministic agentsProceduresCredentials
Book a Demo

Related use cases

More use cases

  • Employee onboarding automationStepwork reads new hires from your HR system, creates their accounts, sets up every app in their bundle, including ones without SCIM, and tells the manager what's ready.Learn more
  • Employee offboarding automationStepwork starts offboarding when HR records a termination, closes every app including ones without SCIM, hands files to the manager, and records when access ended.Learn more
  • User access review automationStepwork pulls accounts from every app, including ones without SCIM, matches them to HR, carries out reviewer decisions, and files the evidence in Vanta.Learn more
See all teams

FAQ

Common questions

  • Yes. Modern HR systems like Rippling and Workday send an event when someone is hired, moved, or terminated, and the run starts straight away. Traditional systems like ADP Workforce Now often don't, so Stepwork signs in on a schedule and reads the same report your team downloads today. The steps after that are the same.
  • The rules are the same, and the steps follow each suite. On Microsoft, Stepwork creates the user in Active Directory or Entra ID, assigns the license, and adds Teams and SharePoint groups. On Google, it creates the user in the right org unit and adds the Google Groups that open shared drives and calendars.
  • No. Okta stays the hub, and it keeps pushing every app it supports through SCIM. Stepwork sets up the profile and department groups from your HR system, then covers the apps Okta assigns but can't create accounts in, and the steps outside identity, like devices, files, and records.
  • A rule card reads a field from your HR system, like the department, and sends each person down the path for it. A simple procedure has one rule with two paths. A larger one can route Engineering, Sales, and Finance to their own steps, check whether a role is privileged, and ask a manager to approve before anything is granted.
  • The old department's groups and app roles come off first, then each app in the new bundle is granted. Privileged roles wait for the manager's approval in Teams or Slack. Every move leaves a record of what was removed and what was granted.
  • Every run records which accounts were created, changed, or closed, in which apps, on which path, who triggered it, and when. When an auditor asks when a leaver's access ended, the answer is already in the run record.

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.

Illustrative estimate, not a quote. These are example volumes and typical hand times, not a customer's results. Your numbers will differ, and we can work them out with you.
The manual taskTimes a weekMinutes eachHours a week
Create the account, license, and department groups5201.7
Add a user to an app without SCIM3063
Swap a mover's groups and app roles3452.3
Offboard a leaver across identity, apps, and devices3603
Pull access evidence for an audit request2301
Hours a week
11
Hours a year
546
Of one full-time person
27%
Example volumes, not a customer's numbers. Minutes are the typical time to do each task by hand. Hours a year assume 50 working weeks.

See it run on a process you already repeat

Bring one. We will show you what it looks like as a flow and what each run records.

Book a Demo
Stepwork

Deterministic agents for work that must run the same way every time.

Product

  • Procedure
  • Extractions
  • Marketplace

Solutions

By team
  • IT
  • Security & Compliance
  • Finance & Accounting
  • Sales & RevOps
  • Operations
  • HR & People
By industry
  • Healthcare
  • 3PL and warehousing
  • Freight and trucking
  • Fuel and convenience stores
  • Construction
  • Manufacturing and distribution
  • Accounting firms
  • Field services and trades
  • MSPs

Capabilities

  • Deterministic Agents
  • Stepwork MCP
  • Containers
  • Ask Bob

Company

  • Security
  • FAQ

Resources

  • AngelList Case Study
  • Claude Co-Work Alternative
  • Free IT Ticket Analysis
  • Stack check
  • For AI tools (llms.txt)

Legal

  • Terms and Conditions
  • Privacy Policy
  • Data Processing Agreement
  • Subprocessors

Ask your AI about this page

  • ChatGPT
  • Claude
  • Perplexity

2261 Market Street #4481, San Francisco, CA 94114, USA

Loot Discount inc dba Stepwork

© 2026 Stepwork. All rights reserved.