Use Case: Automate the BetterCloud for G Suite Deprovision Tool


If you've ever utilized the Deprovision Tool in BetterCloud for G Suite, you'll know that it provides a comprehensive offboarding process for all available aspects of a Google user account, saving management time and reducing the risk of data loss. This process can now be automated with Workflows, eliminating all previously manual steps and reducing the burden of detailed account management on the part of your domain administrator.

While manual actions available in the new BetterCloud app provide full feature parity with the Deprovision Tool in BetterCloud for G Suite, please note that certain actions cannot yet be automated in a manner that provides flexibility across teams: for example, when adding the "Copy Group Memberships" action, you must specify both the "from" and "to" user accounts, which won't support deprovisioning multiple accounts. Therefore, these actions have not been included in the template below, but future roadmap enhancements will help address our app's functionality in these scenarios. 


To mimic all steps from the Deprovision Tool, you'll need to select the following actions for your workflow: 

  • Hide/Show User in Directory 
  • Reset Password
  • Set User’s Auto-Reply 
  • Delegate User’s Email
  • Transfer Drive Files 
  • Transfer Sites 
  • Transfer Secondary Calendars
  • Delete All Calendar Events
  • Revoke User’s Apps
  • Transfer Group Ownership 
  • Suspend User

You'll also need to select a triggering event (WHEN) and qualifying condition (IF) that you can execute, in order to trigger the automation of these workflow actions. An event we really like is when "User's Org Unit Changes", and if "Org Unit is". This will allow you to trigger your workflow by moving your users destined for offboarding into a new org unit, which you can further automate in bulk with our Bulk Edit Users tool in BetterCloud for G Suite. 

You can see a full list of G Suite events, conditions and actions here.

Here's an example of what this finished workflow build will look like: 


Important / Requirements

  • Some of the actions listed above require that the affected user's account exist in an active state. As workflow actions are executed in numerical order, you must place the "Suspend User" action at the end of your list of workflow actions to avoid failures.
  • You can further customize this workflow template to suit your organization's needs! Get creative and explore actions offered through other connected apps
Was this article helpful?
0 out of 0 found this helpful
Have more questions? Submit a request