Imports users, groups, Chrome OS devices, and sign-in logs from your Google Workspace organization.
For the general flow of adding a source, see Connect Data Sources.
Before you start
Google Workspace account with Super Admin role
Access to Google Cloud Console
Step 1 — Create the project and enable the Admin SDK API
console.cloud.google.com → create or select a project
APIs & Services → Library → search Admin SDK API → Enable
This API covers both the directory and sign-in logs. Without it, requests fail with 403.
Step 2 — Create a GCP service account
IAM & Admin → Service Accounts → Create Service Account
Name: harven
Keys → Add Key → JSON → download the file
Note the service account Client ID
Step 3 — Enable Domain-Wide Delegation
Service account details → Enable G Suite Domain-wide Delegation
In admin.google.com → Security → API Controls → Domain-wide delegation
Add the Client ID with scopes:
admin.directory.user.readonly, admin.directory.group.readonly, admin.directory.device.chromeos.readonly, admin.reports.audit.readonly
Step 4 — Remediation actions (optional)
Only required to suspend / reactivate a user from HARVEN
Add the write scope to the domain-wide delegation:
admin.directory.user
Without .readonly: read + write access. Omit it if you only use read-only import.
What to enter in HARVEN
Delegated Email — Super Admin email for impersonation (Your Super Admin account email)
Service Account Key — JSON content of the downloaded key file (GCP → Service Accounts → Keys → download JSON)
What HARVEN reads
user — Google Workspace users: identity (userid, name, email, workspace_admin), security (mfa_enabled, last_password_change)
device — Chrome OS / mobile devices: device (name, manufacturer, model, os, osversion, last_signin)
signin — Sign-in logs: connection (status, date, application, ip_address, failure_reason)
group — Google Groups: group (id, name, type)
Official documentation
Need help? Contact [email protected].