<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Google Connector on</title><link>/configuration/sources/google/</link><description>Recent content in Google Connector on</description><generator>Hugo</generator><language>en</language><atom:link href="/configuration/sources/google/index.xml" rel="self" type="application/rss+xml"/><item><title>Gmail Connector Setup</title><link>/configuration/sources/google/gmail/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>/configuration/sources/google/gmail/</guid><description>&lt;h3 id="installing-the-gmail-connector"&gt;Installing the Gmail Connector&lt;/h3&gt;
&lt;blockquote&gt;
&lt;p&gt;&lt;strong&gt;Note:&lt;/strong&gt;
For this step, your deployment engineer will be required.&lt;/p&gt;
&lt;/blockquote&gt;
&lt;p&gt;The Gmail and Google Drive connectors depend on a shared Google Workspace configuration section. Google Workspace requires three properties to be set during configuration:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;&lt;code&gt;ProjectID&lt;/code&gt; must reference the project &lt;a href="https://console.cloud.google.com/cloud-resource-manager?pli=1"&gt;created in GCP&lt;/a&gt;. The id, not the name, must be specified.&lt;/li&gt;
&lt;li&gt;&lt;code&gt;ServiceUser&lt;/code&gt; is currently a reference to a super user or administrator within your organization. For example, the primary IT email. This may change in the future.&lt;/li&gt;
&lt;li&gt;&lt;code&gt;ServiceAccountKey&lt;/code&gt; is the base64-encoded string as obtained during initial install of the Google source.&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;To obtain the service account key, your deployment engineer will run the following Terraform command:&lt;/p&gt;</description></item><item><title>Google Drive Connector Setup</title><link>/configuration/sources/google/gdrive/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>/configuration/sources/google/gdrive/</guid><description>&lt;h3 id="installing-the-google-drive-connector"&gt;Installing the Google Drive Connector&lt;/h3&gt;
&lt;blockquote&gt;
&lt;p&gt;&lt;strong&gt;Note:&lt;/strong&gt;
For this step, your deployment engineer will be required.&lt;/p&gt;
&lt;/blockquote&gt;
&lt;p&gt;The Gmail and Google Drive connectors depend on a shared Google Workspace configuration section. Google Workspace requires three properties to be set during configuration:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;&lt;code&gt;ProjectID&lt;/code&gt; must reference the project &lt;a href="https://console.cloud.google.com/cloud-resource-manager?pli=1"&gt;created in GCP&lt;/a&gt;. The id, not the name, must be specified.&lt;/li&gt;
&lt;li&gt;&lt;code&gt;ServiceUser&lt;/code&gt; is currently a reference to a super user or administrator within your organization. For example, the primary IT email. This may change in the future.&lt;/li&gt;
&lt;li&gt;&lt;code&gt;ServiceAccountKey&lt;/code&gt; is the base64-encoded string as obtained during initial install of the Google source.&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;To obtain the service account key, your deployment engineer will run the following Terraform command:&lt;/p&gt;</description></item><item><title>Google Sites Connector Setup</title><link>/configuration/sources/google/gsites/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>/configuration/sources/google/gsites/</guid><description>&lt;h3 id="installing-the-google-sites-connector"&gt;Installing the Google Sites Connector&lt;/h3&gt;
&lt;blockquote&gt;
&lt;p&gt;&lt;strong&gt;Note:&lt;/strong&gt;
For this step, your deployment engineer will be required.&lt;/p&gt;
&lt;/blockquote&gt;
&lt;h4 id="prerequisites"&gt;Prerequisites&lt;/h4&gt;
&lt;p&gt;Google Sites Connector requires you to enable Google Vault for your organization. Google Vault enrollment details are available in &lt;a href="https://support.google.com/vault/answer/2584132?hl=en"&gt;the official documentation&lt;/a&gt;&lt;/p&gt;
&lt;p&gt;You will need a Service Account as described in &lt;a href="/configuration/sources/google/#grant-service-account-permissions"&gt;Grant Service Account Permissions section&lt;/a&gt;. In addition to the scopes listed there, you must grant the following scopes to the Service Account:&lt;/p&gt;
&lt;pre tabindex="0"&gt;&lt;code&gt;- https://www.googleapis.com/auth/ediscovery
- https://www.googleapis.com/auth/devstorage.read_only
&lt;/code&gt;&lt;/pre&gt;&lt;p&gt;Vault API access must be manually enabled by the GCP project associated with the Service Account. This can be done via GCP API Console, by following &lt;a href="https://support.google.com/googleapi/answer/6158841?hl=en"&gt;the steps&lt;/a&gt; in the official documentation.&lt;/p&gt;</description></item></channel></rss>