Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

  1. Select Connections > Add connection.

  2. Select Google Workspace as the platform on the Add connection modal.

  3. Enter the connection information. Reference the table below for details about each field.

  4. Test the connection to ensure DryvIQ can connect using the information entered.

  5. 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.)

  6. Select Done.

Add connection modal - Google Workspace

...

Field

Description

Required

Display as

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.

Optional

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

Required

Private key

Enter the x509 private key. 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-----.

You can click the Choose a file on your computer link to import the key from a file on your computer. Use the file upload dialog that appears to locate the file that contains the key you want to use. 

Required

Subject email

Enter the email address for the account whose data will be transferred. This is the "sub" claim on the JSON Web Token that DryvIQ will use to connect with Google Workspace.

If you create a job using impersonation (“run as”), that setting will override the account added here.

Required

Drive Space

Select the level where the connection should be made.

My Drive: This is the default entry. When selected, the connection will be made at the "My Drive" (the highest) level of the account.

Unorganized: Selecting this option creates the connection to the unorganized content in the account. Unorganized files are files that are orphaned. This means the file exists but isn’t a part of a file structure. This happens when parent folders get deleted. These files can only be found by searching the drive for "is:unorganized owner:me." 

Shared with me: This creates the connection to the shared content (content available through the "Shared with me" menu option within the account).

Domain

Enter the target domain name. For example, your-domain.com.

If you do not include the domain for the Subject Email, you must include the domain in this field. This domain will then be used as the domain for the account.  

Optional

Token uri

Enter the custom authentication URI. If not supplied, the default is used - https://accounts.google.com/o/oauth2/token.

Optional

Preserve content type

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. 

Optional

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.

Optional

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.

Optional

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.  

Optional

Read-only Access

Specify if the connection should be created with read-only access.

The default value is No. This means the connection will be created with the full access granted to the account used to create the connection.

Selecting Yes creates the account with read-only access. The configuration for the Google account used to create the connection must match the access level for the read-only access to properly be applied.

Optional

Impersonate Owner During Delete

Indicate if you want DryvIQ to impersonate the item owner when performing deletes.

The default value is No. This means that DryvIQ will attempt to delete an item as the current impersonated user. If the user does not own the item, DryvIQ will not be able to delete it. You will need to delete the item manually.

Selecting Yes allows DryvIQ to impersonate the item owner so the item can be deleted. This reduces the number of manual deletions you need to complete.

Google does not support impersonating external users, so DryvIQ cannot delete items owned by external users. The delete will fail, and you will need to delete the item manually.

Optional

...

The Google Workspace connector uses per-request impersonation. When Google Drive Workspace is the source or destination connection, DryvIQ must make requests to the platform on behalf of the account owner, not the administrator. To ensure “Created By” and “Modified By” dates are preserved during migration, the destination connection must also impersonate the corresponding account owner.

...