Testing Your Inactivity Workflow
Last updated: October 8, 2024
Background
Inactivity workflows can save you time and money - yes! You read that right - both time AND money all rolled up into a bundle that we call Inactivity Workflows.
If you've read through📄 Inactivity Workflows 101then you already know the benefits. Now it's time to test your flow before releasing it into the wild.
Follow these easy instructions and you'll be ready to go in no time!
Steps
A great way to test your inactivity workflow is to try it on accounts with very long inactivity times.
A user who hasn't logged into a service for 365+ days, for example, likely won't complain if their access is removed and should be safe to use for testing scenarios. 😛
Below are the steps for testing your workflow on these types of accounts.
1. Go to the Accounts tab for the app you want to test.
2. Filter the Account Status column to "Active", then click on the Last Login column header to sort by last login and find accounts with the longest inactivity window.
3. Find the inactivity threshold you want to use for testing.
As an example, if you see only 2 accounts with inactivity greater than 180 days and you want to use those for testing, then your threshold will be 180 days.
4. Adjust the following settings for your inactivity workflow.
Excluded Users: Remove any application or service accounts that may not log into the service ever, to ensure these aren't accidentally removed or deactivated. You may also want to remove executives from consideration. 🙂
Notification Flow: Set this to "Workflow Reviewer".
Workflow Reviewer: Set this to yourself, or any other teammates who want to test the alerts.
Inactivity Time: Set it to the value you determined above in step 3.
See📄 Creating An Inactivity Workflow