Google Workspace Configuration
GOOGLE WORKSPACE ADMIN
Relationship Intelligence reads authorized directory and message metadata using a tenant-specific Google service account with Domain-Wide Delegation.
Before continuing, complete Google Cloud Service Account Setup and have the numeric OAuth Client ID available.
1. Open Google Admin Console
- Sign in as a Google Workspace Super Admin.
- Open Security → Access and data control → API controls.
- Select Manage Domain-Wide Delegation.
- Select Add new.
2. Authorize the service account
Client ID — paste the numeric OAuth Client ID displayed by EIE or Google Cloud Console.
OAuth scopes
https://www.googleapis.com/auth/admin.directory.user.readonly
https://www.googleapis.com/auth/admin.directory.domain.readonly
https://www.googleapis.com/auth/gmail.metadata
Select Authorize.
| OAuth scope | Purpose |
|---|---|
admin.directory.user.readonly | Reads directory user identities and attributes |
admin.directory.domain.readonly | Reads authorized domain information |
gmail.metadata | Reads Gmail headers and metadata without requesting message-body scope |
Copy the scopes exactly. Separate multiple scopes with commas if Google Admin Console requires a single comma-separated entry. Do not add broader Gmail, Drive, Calendar, or directory scopes unless a future Real Intelligence release explicitly requires them.
3. Confirm the delegation entry
Verify that:
- The numeric Client ID matches EIE
- All three required scopes are present
- There are no typing errors or spaces inside the scope URLs
- The delegation entry is active
4. Verify from EIE
EIE → Connected Systems → Google Workspace → Verify
| Check | Expected result |
|---|---|
| Service-account credentials | Valid |
| Domain-Wide Delegation | Verified |
| Directory API | Operational |
| Gmail API | Operational |
| Google Customer ID | Populated |
| Workspace domain | Matches tenant |
| Test mailbox | Accessible |
Google authorization changes can sometimes take a short period to propagate. If a check fails immediately after authorizing, wait briefly and verify again.
Then run the Salesforce end-to-end test: Verify Google Connection.
Was this helpful?
Last updated 1 month ago