Use Case: Four Quick Deprovision Examples

Follow

Sometimes a user account needs to be deprovisioned, restricted in its access, or deleted quickly, due to a security breach or other critical event. In these cases, locking down the account in question is of primary importance, and you may not wish to spend valuable time on a full deprovision process.

In this article, you'll find outlines of a few use cases regarding the quick deprovision or offboarding of user accounts, and the workflow templates you can use to achieve and automate these results.

Deprovisioning


I have several phases of my deprovision process. I have a restricted org unit called “Deprovision”, and when I place users there, I want to make sure their access is immediately revoked.

  • When any user is placed in the “Deprovision” org unit, reset their password, delete 2-step backup codes, and hide them in the Directory.


I have several phases of my deprovision process. I have a restricted org unit called “Deprovision”, and when I place users there I want to suspend their account, hide them in the directory, and delete their backup codes (just in case).

  • When any user is placed in the deprovision org unit, suspend them, hide them in the directory, and delete their backup codes.


I only suspend users that I’m about to deprovision. When I suspend a user, I want to make sure their access is immediately revoked.

  • When any user is suspended, place them in the “Deprovision” org unit, hide them in the directory, reset their password, and delete their 2-step backup codes.


I have a very high turnover and need to delete many users every month. I want a way to automatically delete users placed in a particular org unit.

  • When any user is added to the “Delete” org unit, delete the user.

Was this article helpful?
1 out of 1 found this helpful
Have more questions? Submit a request