Skip to content
Call wiki

Can Drive search find files someone edited, not just owns?

Last updated 2026-08-17 · Confidence: documented — Google’s Drive search references, file-field docs, and Activity API docs; what the Claude connector’s own tools return is inferred.

No search filter finds files by who edited them — not in Drive’s UI, not in the API query language. What works: filter by modified date, then check each hit’s last-modifying-user metadata; or use the Drive Activity API, which connectors don’t expose. So make the pull conditional in the prompt.

Search filters people by permission, not activity

Section titled “Search filters people by permission, not activity”

Drive’s people operators — owner:, creator: (shared drives), to:, from:, sharedwith: — all match ownership and sharing, per the advanced-search help page. The API query language is the same: writers matches users “who have permission to modify the file”, not those who did, and no query term covers actual editors. A “last modified by” search is a standing feature request.

Metadata names the last editor — one file at a time

Section titled “Metadata names the last editor — one file at a time”

Every file carries lastModifyingUser — “the last user to modify the file”. The workable pattern: query a folder for modifiedTime > cutoff, then read each hit’s metadata and keep the person’s files. A later edit by someone else hides theirs; revisions.list closes that gap with a last-modifying user per revision.

The Activity API has the real answer

Section titled “The Activity API has the real answer”

The Drive Activity API returns per-action history — edit, rename, comment, each with actor and timestamp — for one file or a whole folder subtree. Its query filter takes only time and action type, so narrowing to one person happens after the query. Visibility follows permissions: only files you can access show activity.

What a connector reaches

Section titled “What a connector reaches”

Claude’s Drive connector does keyword search, reading, and a recent-files listing — no Activity API. Its listing sorts by “last modified by anyone” or “by me”, never by a named third person (tried — the tool’s own definition, Aug 2026). Whether its metadata tool returns the last modifier decides if the pattern above works. Hence the conditional prompt: “if possible, identify which files and save those; if not, don’t” — the agent skips cleanly instead of guessing.

Q&A from calls

Section titled “Q&A from calls”

Can the Drive connector identify the files a teammate touched, not just created? Not with a search filter — none exists. Approximately, yes: list files modified since a cutoff and check each one’s last-modifying-user metadata. Keep the request conditional so the agent skips it when its tools lack that field.

Sources

Section titled “Sources”