Sharing is easy. Un-sharing is a project.

Drive Auditor exists because Google Drive makes granting access a single click and taking it back nearly invisible.

Drive Auditor started the way most small tools do: with a problem the existing screens couldn't answer. After a few years of client handoffs and "here, I'll just share the folder" moments, a simple question had no simple answer: who can see my files right now?

Drive can tell you, but only one file at a time, through a dialog designed for adding people rather than reviewing them. There was no way to look at a folder of five hundred files and see the whole picture: the forgotten public links, or the contractor from two projects ago who could still open everything.

So this tool does exactly that one job. It walks a folder tree, records who holds what on every item, and presents it the way you actually think about access: person by person, not file by file. A report you can't act on is just bad news, so it also lets you revoke, and un-revoke, from the report itself.

Principles

• Least privilege, both ways. The point of the product is helping you enforce least privilege in your Drive, so it practices it too. Sign-in is read-only. You grant write access separately, only at the moment you revoke something.
• Reversible by default. Access reviews involve judgment calls, and judgment calls get revised. Every unshare records the original role so it can be restored with one click, without sending anyone a notification email.
• Report what's true, not what's inferred. Labels like "inherited" and "direct" come from Drive's own permission details, read at scan time. When something can only be inferred, the report says so.
• Your data stays yours. Scan reports live in your account and you can delete them at any time. Deleting a scan removes its data from storage. There is no shadow copy.

The state of things

Drive Auditor is a small product in active development, not yet open to the public. The scanning, per-person reports, revocation, rescan, and scan-diff features described on the front page are built and working. We're bringing people in from the waitlist as we finish verifying everything in production. Once you're in, if you hit something rough, the security page explains what's happening under the hood. The product improves fastest when people ask hard questions about it.