Once you create a SaaS user workflow, you can create an offboarding workflow for inactive SaaS users.
Your ability to identify inactive SaaS users by their last login activity depends on the integration you are using. Click here and search for your integration from the list to check if this functionality is available.
You need to create a SaaS user workflow that identifies inactive or underutilized users by following the steps in Creating SaaS user workflows.
Prior to offboarding the SaaS user, it is important to "clean up" the user in the external SaaS system. For example, transferring opportunities to the user's supervisor, and allocating the user's folders to another coworker.
Creating the offboarding workflow
- Click Configuration > Workflows
- Click Add (+) and select Software SaaS Users from the list.
- Enter the name of the workflow.
Editing the begin block
The begin block is the workflow’s trigger. In the example below, the begin block retrieves Salesforce users who have not logged in in the past 60 days. Additional rule criteria are added to the begin block to ensure that the user exists and is active.
- Click Edit.
- Enter the name of the begin block.
- Configure the schedule to run daily or hourly. This will ensure timely deleting of the user in the external system.
- The workflow should run for Active records by default.
- Click Add Rule and add the following rules:
- SaaS name Equals Salesforce.
- Last activity date Before 60 [days].
- Deactivated Equals No
- User identifier in SaaS Is not Empty.
- Click Save.
Learn more about the Begin block
Adding the API block
- Click the Blocks tab, and drag and drop the API block onto the canvas.
- Click Edit .
- Search for your SaaS integration, such as Salesforce.
- Choose a delete or deactivate user preset from the list such as Salesforce Deactivate user.
- To select your preset, click the right arrow>.
- Add the required information in the Configure section
Click the documentation link to learn more about the configuration steps.
Add your positive and negative exits to the block. For example, you may wish to add:
- Another API block, such as the Okta Deactivate User or Jira Delete User block. Make sure that the Last activity date you have chosen in the Begin block complies with your data retention policy for all SaaS systems. Otherwise, create separate workflows for each Last activity date.
- A Notify block to create an offboarding notification.
- An Archive block to deactivate the user in Oomnitza.
- An Update block to update the user's status.
- An Offboard Licenses, Offboard Accessories, or Offboard Assets block, to unassign the user from a device or software license.
Running the workflow
- Click Save and connect the blocks
- Validate the workflow and Activate it so that the workflow is live in your system
Inactive users matching the criteria in the begin block are automatically offboarded from the external SaaS system once the integration is run.