The Google Shared Drives connector in DryvIQ allows you to analyze, migrate, copy, and synchronize files between your Google Shared Drives and cloud storage repositories and on-premise network file shares. The first step is to create the Google Shared Drives connection by providing the connection information required for DryvIQ to connect to the shared drives.
Creating connection | User Interface
Select Connections > Add connection.
Select Google Shared Drives as the platform on the Add connection modal.
Enter the connection information. Reference the table below for details about each field.
Test the connection to ensure DryvIQ can connect using the information entered.
You will see a "Connection test succeeded" message on the Add connection modal when DryvIQ establishes connection. (If you don't see this message, verify the information you entered.)
Add connection modal - Google Shared Drives
Enter the display name for the connection. If you will be creating multiple connections, ensure the name readily identifies the connection. The name displays in the application, and you can use it to search for the connection and filter lists. The maximum length is 255 characters.
Service Account Email
Enter the email address created during the Service Account creation process. It will resemble <service-account-name>@<project-id>.iam.gserviceaccount.com
Enter the private key required to access the drive. This is the value created when creating the new private key when creating a new Service Account in the Google IAM & admin Console. It will begin with "-----BEGIN PRIVATE KEY-----" and end with "-----END PRIVATE KEY-----."
Enter the email address for the root account containing the data to be transferred.
Indicate if DryvIQ should try to preserve files in their original content type. This feature is mainly used for Google to Google transfers.
The default value is No. This means that an upload content type is not specified. Most files will still preserve content types. However, Google native documents and Microsoft Office files will transfer as Microsoft Office files.
Selecting Yes will preserve files in their original content type. Google native documents will transfer as Google native documents. Microsoft Office files will transfer as Microsoft Office files.
Import as Google native documents
Indicate if DryvIQ should import Microsoft Office documents as Google documents. This feature is mainly used when transferring from any platform, such as Box to Google.
The default value is No. This means Microsoft Office files will be preserved as their original content type.
Selecting Yes will import all Microsoft Office files as Google native documents.
Behavior when deleting files
Select the type of delete DryvIQ should perform when deleting items: Permanent or Soft. Soft delete is the default delete behavior; however, Permanent is the recommended behavior.
A soft delete marks items as a deleted. You can still access them to restore or permanently delete the items.
A permanent delete removes the items. This delete is not reversible.
Allow file discovery
Indicate if files with shared links should be searchable.
The default value is No. This means that only users with whom the file has been shared can find and access the file.
Selecting Yes sets the "People can search for this file" setting in the file link settings to TRUE. This means any files with shared links can be found and accessed by any user through the search.
Use domain admin access
Indicate is you want to allow domain-level administrator access to all Google shared drives, regardless of membership.
The default value is No. This means the connection can only access shared drives the administrator is a member of.
Selecting Yes allows the connection to access all shared drives in the administrator's domain/enterprise.
Features and Limitations
Platforms all have unique features and limitations. DryvIQ’s transfer engine manages these differences between platforms and allows you to configure actions based on Job Policies and Behaviors. Utilize the Platform Comparison tool to see how your integration platforms may interact regarding features and limitations.
Files and Folders
Below is list of supported and unsupported features as well as additional file/folder restrictions.
DryvIQ supports author preservation in Shared Drives. It does this by impersonating the user that last modified the file when uploading the file. However, there are some limitations:
The impersonating author must have access to the shared drive. If the shared drive and its permissions are transferred by the job, the source must have these permissions in place in the corresponding folder.
DryvIQ cannot preserve the audit trail of external or deleted accounts since they cannot be impersonated.
Google Shared Drive Limits
Google limits the number of items, members, and daily uploads you can have in shared drives. Refer to Google's Shared drive limits documentation for more information.
Google does not impose restrictions for the total path length.
Segment path lengths are limited to 500 character. Segments are delimited by a forward slash (/). For example, <max 500 characters>/<max 500 characters>.
In Shared Drives, DryvIQ can assign the following permissions:
Permissions are supported at the Shared Drive level (membership)
A Shared Drive is comparable to a SharePoint Library.
Permissions for folders within the Shared Drive are supported.
Permissions for files within the Shared Drive
External/Internal file permissions can be added if they are not a part of the membership, but this must be configured in Shared Drives before it will work.
Google shared Drives also has the following restrictions and limitations for content. DryvIQ will handle the content as indicated.
Non-Transferable File Types and Elements
The following file types and elements cannot be transferred.
Sites, Forms, Fusion Tables, My Maps, and Google Workspace Marketplace are all files that are not transferable.
Comments in Docs, Sheets, and Slides are not transferable.
You cannot transfer permissions to folders other than the shared drive.
You cannot transfer demoting/deny permissions (disinheritance).
Native Google documents will be handled as indicated below.
Although some platforms such as Box and Dropbox support Google Docs, DryvIQ does not currently support transferring them to Google Shared Drives.
When transferring Google Docs from Google Shared Drives to another platform, DryvIQ will export the documents as Microsoft Office documents.
Google Docs convert to docx files.
Google Slides convert to pptx files.
Google Sheets convert to xlsx files.
Google Drawings converts to svg files.
Google Apps Script converts to json files.
Google Forms, Fusion Tables, Sites and My Maps are not available for download in Google Shared Drives. This means DryvIQ is prevented from transferring these items. Expected behavior is the item will be flagged with the error message "IO Violation and message:Downloading content is not supported for file...".
Microsoft Office Documents
When transferring Microsoft Office documents to Google Shared Drives, you can choose to either keep their original format or import them as Google Docs when setting up the connection.
Root File Transfers
You cannot transfer files to the root of your Google Shared Drives connection. Folders transferred to the root of the Google Shared Drives connection will be created as Team Drives.
Create connection | REST API
The sample code below shows how to create a shared drives connection that uses impersonation. Make sure the following fields are set accordingly.
The client_email should be the Google Workspace Admin Service Account.
The subject should be the email for the user you would like to impersonate.