Skip to content
Connection Guide

Connect Google Drive Without Breaking the Audit Trail

Use this guide to connect Google Drive or confirm the export-based path that fits your environment. Aurora keeps source, timestamps, ownership, and collection history attached so the first run becomes reusable proof instead of one-off setup work.

Connector Summary
Connection typeDirect connection
CategoryEvidence
Checklist4 steps
Want help with rollout?
We'll confirm what can be automated, what stays export-based, and how to keep the first evidence record clean.

First-Run Checklist

Use this sequence to connect Google Drive and make sure the first collection lands cleanly.

  1. 1
    Enable Drive API for the Google Cloud project that owns the service account.
  2. 2
    Enable Google Workspace domain-wide delegation for the service account and authorize only the required Drive read scopes.
  3. 3
    Store service_account_json securely and configure admin_user_email for impersonation.
  4. 4
    Validate file listing and artifact retrieval before enabling scheduled sync.

Credentials and Secrets

The keys, secrets, or tokens Aurora uses to authenticate and collect proof.

service_account_json

Recommended Access

Aurora only asks for the minimum read access needed for collection and checks.

Access requirements depend on the collection mode and scope you choose.