Search documentation

Search all documentation pages

Google Drive Integration

Enforce document compliance and access control on Google Drive.

Overview

The Google Drive integration connects Aguardic to your Google Workspace via OAuth. Aguardic monitors file activity in your Drive, evaluating document content, metadata, and sharing settings against your policies. Violations trigger enforcement actions like quarantining files or adding comments.

Setup

1. Connect via OAuth

Go to Integrations > Add Integration > Google Drive in the Aguardic dashboard and click Connect. You'll be redirected to Google to authorize Aguardic with the required Drive API permissions.

2. Configure Monitored Paths

After connecting, configure which folders Aguardic should monitor. You can watch specific folders or your entire Drive.

Monitored paths let you scope governance to specific folders, such as a shared "Legal Documents" or "Customer Data" folder, rather than scanning every file in your Drive.

3. Bind Policies

Go to Policy Bindings and map your policies to the Google Drive integration. Policies are evaluated against file activity within your monitored paths.

4. Configure Enforcement

Choose how Aguardic enforces policy results on Google Drive:

  • BLOCK — Moves the file to the "Aguardic Quarantine" folder and adds a comment explaining the violation
  • WARN — Adds a comment on the file with violation details, keeping the file in place
  • MONITOR_ONLY — No visible action in Google Drive, violations logged in Aguardic only

How It Works

  1. A file is created, modified, or shared in a monitored folder
  2. Google sends a push notification to Aguardic via webhook
  3. Aguardic fetches the file content, metadata, and sharing settings
  4. The governance engine evaluates against bound policies
  5. Enforcement actions are taken based on the policy mode

Aguardic automatically creates the "Aguardic Quarantine" folder in your Drive when the first BLOCK enforcement is triggered.

What Gets Evaluated

  • File content — Text extracted from documents, spreadsheets, and presentations
  • File metadata — Name, type, size, creation date, last modified date
  • Sharing settings — Who the file is shared with, link sharing status, permission levels
  • File owner — Who created or owns the file

Example Policies

Sensitive Data in Documents

Detect PII or confidential data in document content:

  • Field: content
  • Operator: MATCHES
  • Value: (\b\d{3}-\d{2}-\d{4}\b|CONFIDENTIAL|patient.record)
  • Severity: CRITICAL

Public Sharing Detection

Flag files that are shared publicly via link:

  • Field: sharing
  • Operator: EQUALS
  • Value: anyone_with_link
  • Severity: HIGH

File Naming Convention

Enforce consistent file naming in governed folders:

  • Field: filename
  • Operator: MATCHES
  • Value: ^[A-Z]{2,4}-\d{4}-.*\.(pdf|docx|xlsx)$ (e.g., HR-2024-benefits.pdf)
  • Severity: LOW

Next Steps