Google Workspace Integration
Connect QuantAssure to Google Workspace to monitor user security settings and compliance.
What It Collects
- User Directory — All users in your Google Workspace domain as assets
- Security Compliance — Security configuration findings
including:
- Users without 2-factor authentication enabled
- Users with admin privileges
- Recently created accounts
- Other security compliance gaps
Prerequisites
- Google Workspace admin access
- A Google Cloud Platform (GCP) project
- A service account with domain-wide delegation
-
Required OAuth scopes:
-
https://www.googleapis.com/auth/admin.directory.user.readonly
-
Setup Steps
1. Create a GCP Project
- Go to the Google Cloud Console
- Create a new project (or use an existing one)
- Note your project ID
2. Enable Required APIs
- In your GCP project, go to APIs & Services → Library
- Search for and enable Admin SDK API
3. Create a Service Account
- Go to APIs & Services → Credentials
- Click Create Credentials → Service account
- Name it (e.g., "QuantAssure")
- Grant it the Editor role (or a custom role with Admin SDK access)
- Click the service account to edit it
- Go to Keys → Add Key → Create new key → JSON
- Save the JSON key file — you'll need this
4. Configure Domain-Wide Delegation
- In the service account details, find Domain-wide delegation and note the Client ID
- Go to your Google Workspace Admin Console
- Navigate to Security → API Controls → Domain-wide delegation
- Click Add new
- Enter the service account Client ID
-
Add the required scope:
https://www.googleapis.com/auth/admin.directory.user.readonly - Click Authorize
5. Configure in QuantAssure
- Create or edit a System in QuantAssure
- In the Data Sources section, enable Google Workspace
- Enter your Workspace domain (e.g.,
yourcompany.com) - Upload or paste your service account JSON key
- Save your system configuration
6. Run Your First Scan
Click "Run Scan" to collect data from Google Workspace.
What to Expect
After your first scan:
- Assets: One asset per user in your Workspace domain
- Findings: Security compliance violations:
- Users without 2FA enabled
- Users with super admin privileges
- Suspended or recently created accounts flagged for review
Troubleshooting
"Insufficient permissions" error
- Verify domain-wide delegation is configured correctly
- Check that the OAuth scope is added in Admin Console
- Ensure the service account key is valid
No users appearing
- Verify your domain is correct
- Check that the service account has Admin SDK access
- Confirm domain-wide delegation is authorized for the correct Client ID
Missing compliance findings
- 2FA status requires directory read access
- Some user attributes may require additional scopes