Onboarding and offboarding from one message
Tell it who is joining or leaving. It drafts the full plan from the person's team and role, waits for your IT lead to approve it, then does the work.
Last updated 6 October 2026
The problem
Onboarding means a dozen accounts and groups created in the right order before day one. Offboarding means removing every one of them on the last day, which is where forgotten access becomes a security risk.
Both are checklists that live in someone's head or a spreadsheet, so they vary from person to person.
How the AI ITSM Agent does it
- 01
Someone tells it in Slack
"Alex joins the sales team on Monday" or "Sam's last day is Friday."
- 02
It drafts the plan
From the team and role it lists the accounts, groups and apps to create or remove, based on your playbook.
- 03
Your IT lead approves the plan
Nothing changes until the plan is approved.
- 04
It does the work and reports back
It creates or removes the access in Okta, hands anything it can't do (like shipping a laptop) to a person, and records every step.
Example
Guardrails
- Every plan is approved before anything changes.
- Offboarding removes access on the date you set, not when someone remembers.
- Steps it can't do are handed to a person with the context attached.
Works with
See the AI ITSM Agent do this with your own tools.
Book a demoQuestions
Can it start from our HR system?
Not yet. Today it starts from a message in Slack, such as "Alex joins Sales on Monday".
What about laptops and hardware?
It raises the request for your IT team with the details filled in, so nothing is forgotten.
Related
Hire your first AI employee
Tell us which team needs one, and we'll show you how it works with your tools.