Use case: employee offboarding
When someone leaves, several teams each have a part to play, and the gaps between them are where things go wrong: an account left open, a laptop never returned, a policy applied to one leaver and not the next. With Floxar, offboarding is one flow that moves across teams, with an AI agent taking the repeatable work and every team's part recorded on the same trail.
The parts involved
| Layer | In this case |
|---|---|
| Trigger | HR starts the offboarding flow for the leaver |
| Agent | An agent that removes access across systems |
| Process (Floxar) | The offboarding flow: details, access removal, equipment, final pay, close |
| Systems | The identity system and each application the leaver used, the asset register, payroll |
| Credentials | Administrative access for each system, held in the Secrets Vault and granted to the agent only |
| People | HR, IT for equipment, payroll for final pay, the leaver's manager |
How a run goes
- HR starts the run. HR starts the flow and fills in the leaver's details: name, role, last day. Those fields are required, so the run cannot continue without them.
- The agent removes access. The next steps hold the access checklist for the leaver's role, one system per item. The agent removes each account with the credential for that system and ticks the item, so the trail shows exactly what was removed and when.
- IT handles equipment. The flow hands the trail to the IT queue with the agent's note on what was removed. IT records the equipment returned.
- Payroll settles final pay. The trail moves to payroll, who complete the final-pay steps.
- The run closes. When every step is done, the trail is completed. Anything that could not be done, such as unreturned equipment, takes a different path and is recorded as such.
Because the checklist lives in the flow, adding a new application to the access list is a change to one step, and the next offboarding includes it.
What you get from the record
Each offboarding leaves a trail showing who did what and when, across every team involved. That answers the question an audit asks, "was access removed, and when?", without reconstructing it from several systems. Across many runs, analytics show where offboarding waits, usually at a hand-off between teams.
For how runs move between people and agents, see Running and tracking trails.
Last reviewed: 2026-10-06