IT offboarding · Alpha
A disabled account should not hide unfinished work.
HR has not opened a ticket, but the identity provider has already disabled the account. Kebabstack connects that technical signal to a trackable task for IT.
1. Hub receives the change
A configured SCIM or directory connection reports the change for a known person. Direct deactivation in Hub can also trigger the flow. Hub must actually receive the change; Kebabstack cannot detect an unknown identity-provider state.
2. Desk opens a review
With the lifecycle workflow configured, Desk creates a review or reuses an existing open case. A disabled account does not prove that someone has left. An agent checks whether this is a departure or, for example, a temporary suspension.
3. The agent gets relevant context
After offboarding is confirmed and configured approvals are satisfied, assigned computers and other hardware from Assets enter the workflow. Information from connected tools follows their permissions. An unavailable source is shown as missing and does not count as complete.
4. Hardware gets a clear outcome
IT plans return, reuse or sale. A former employee can buy through a private external-buyer dealroom link while their company account stays disabled. Paid does not mean handed over: preparation, release from device management and physical handover are separate steps.
5. People finish the remaining work
Kebabstack helps surface unfinished tasks and record their outcomes. It does not automatically wipe a computer or cancel external SaaS contracts. External accounts, shipping, actual device preparation and company-specific approvals still need a responsible person.
How to evaluate the flow
Use a test person and a test device. Check deactivation, temporary suspension, an already open case and an unavailable data source. Then verify both access rights and outstanding hardware tasks.
Walk through the Desk exampleImplemented alpha. Public source is available under MIT. OpenCloud Marketplace integration is in preparation.