Use cases → Documents and Drive
Audit who can see what across Drive
Enumerate sharing across the domain and surface documents exposed more widely than intended.
| Who it is for | Security, compliance and anyone preparing for a client audit. |
|---|---|
| APIs | Drive API |
| Typical scopes | drive.readonly |
The problem
Link sharing accumulates. Files shared 'temporarily' with an outside party stay shared for years, and nobody has a list.
How it works
- Walk Drive as each user or across shared drives.
- Collect permissions per file, flagging anything public or shared externally.
- Report by exposure level, not by folder.
What changes
A concrete list of what is exposed, ranked by risk rather than by location.
Questions people ask
Can it fix what it finds?
It can, with a write scope — but review first. Automated unsharing has broken live client workflows more than once.
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
Create a client folder structure the moment a deal closes
Provision a consistent Drive folder tree, seeded with templates and shared with the right people, automatically.
Generate documents from a template and real data
Produce agreements, letters and reports from a Docs template with fields filled from your systems.
Sort incoming files into the right place automatically
Watch a drop folder, work out what each file is, and file it where it belongs with a consistent name.