Use cases → Admin and governance
Delegated review of document access logs across tenants
How to audit who accessed critical Drive files using domain-wide delegation, without relying on each admin to pull their own logs.
| Who it is for | Security operations or compliance teams responsible for monitoring file access. |
|---|---|
| APIs | Admin SDK, Drive API |
| Typical scopes | admin.reports.audit.readonly, drive.readonly |
The problem
Manually checking Drive access logs per domain is slow, inconsistent, and usually gets skipped until after an incident. Centralising log review via delegation reduces response time and keeps oversight continuous.
How it works
- Delegate the admin.reports.audit.readonly scope to your service account in each tenant.
- Pull Drive audit logs via the Reports API, filtering for events like VIEW or DOWNLOAD.
- Correlate log entries with file metadata from the Drive API for context.
- Schedule regular exports and flag anomalies for review.
What changes
Access review becomes routine and cross-tenant, with a single workflow able to surface suspicious document access regardless of domain.
Questions people ask
Can I get real-time alerts on document access?
No—there is an unavoidable delay in the Reports API. For true real-time, you would need to build event-driven monitoring into the files themselves, which is not practical at scale.
Is the Drive API itself enough for auditing?
No—the Drive API does not expose access logs. You must use the Admin SDK Reports API with the correct audit scope.
Want this built?
This is a pattern we run in production. We will set up the delegation and build this on top of it — $500 per hour, most of it working the same day.
Talk to us Or read the setup guideRelated use cases
Automate joiners, movers and leavers
Create accounts, set group membership, provision Drive and hand over mailboxes without a manual checklist.
Continuously verify your delegation still works
A scheduled probe that proves every API still answers under every tenant, before a customer finds out otherwise.
Reduce an over-broad delegation grant safely
Find out which scopes your automation genuinely uses, then cut the grant down to them.