Transfer Drive to a manager in Google Workspace
Automatically transfer a departing employee’s Drive files to their manager from a Slack request with Stepwork. Run the Admin data transfer and confirm it completed.
- Use case
- Employee offboardingIT
- Best for
- IT Administrator
- Applications used
Google Workspace
Slack
- Business outcome
- Risk reduction
The problem
The account goes. The files go with it.
When someone leaves, their documents, sheets, and shared folders still sit in their own Drive. If the account is deleted before anyone moves them, the team loses the work.
The data transfer tool in the Google Admin console works, but someone has to set it up for every departure, pick the right manager, and wait for it to finish. On a busy offboarding day, that step is the one that gets missed.
The outcome
The files are with the manager before the account goes
Stepwork runs the Drive transfer and waits until it reads Completed. The files sit with the manager, so employee offboarding can remove the account later without losing the work. The run records who asked and when the transfer finished.
- Drive files move into a folder in the manager’s Drive.
- The run waits until the transfer reads Completed.
- The Slack reply confirms the transfer finished.
The process
From Slack request to files with the manager
When someone leaves, a teammate posts the request in Slack. Stepwork runs the data transfer in the Google Admin console and waits until it completes.
- Step 1
Request it in Slack
A teammate posts the departing employee’s work email and their manager’s in the offboarding channel. Stepwork records who asked and when.
- Step 2
Set up the data transfer
Stepwork signs in to the Google Admin console, opens the data transfer tool, and sets the departing user as the source and their manager as the destination.
- Step 3
Transfer the Drive files
Stepwork chooses Drive and starts the transfer. The files move into a folder in the manager’s Drive.
- Step 4
Confirm it completed
Stepwork checks the transfer until it reads Completed, then posts the result in Slack. The account can be removed later without losing the files.
Why Stepwork
The run stays until the transfer is finished
A deterministic agent sets the departing user as the source and their manager as the destination, then stays with the transfer until it reads Completed. It does not report success while files are still moving.
Similar use cases
Similar use cases
- Suspend user account in Google WorkspaceSigns into the Google Admin console, locates the user, and suspends the account, blocking sign-in while preserving data.
Deactivate user account in OktaSigns into the Okta admin console, locates the user by email, deactivates the account, and confirms the status change ended all SSO sessions.- Deactivate member account in SlackSigns into Slack admin, locates the member, and deactivates their account, removing workspace access.
FAQ