To audit Google Drive sharing links, review files you own or manage, open each file’s Share dialog, and check both General access and the people or groups with access. Set an unnecessary public link to Restricted, then remove direct access that is no longer needed. Check inherited folder access and published copies separately before calling the review complete.

Use Drive in a computer browser and start with a small set of files you are authorized to manage. This is a practical manual review of that set, rather than a promise to inventory every permission across an organization.
Find the right files for your Google Drive sharing links audit
Shared with me contains files others shared with you. It is not a list of everything you have shared. Google documents this distinction in its Shared with me guide.
For a first review, open My Drive and identify the project folders and files you manage. Google’s documented search operators can narrow the candidates:
| Search | What it helps find | What to verify afterward |
|---|---|---|
owner:me | Files you own | Ownership alone does not show whether a file is shared. |
from:me | Documents you shared | Open Share to inspect current access and inherited permissions. |
sharedwith:public | Publicly shared candidates | Confirm General access in the actual sharing dialog. |
owner:me before:2025-01-01 | Older files you own, by modified date | An old modified date does not establish that access is unnecessary. |
Run these as separate candidate searches and combine the results with your known project folders. Some search examples vary by device or account. Do not rely on an undocumented to:all query to prove a complete inventory. The official Drive search reference explains supported operators.
- Select a file you own or manage.
- Inspect General access and direct people/groups.
- Check the parent folder when access is inherited.
- Check any Publish to web setting, then verify the intended access.
Record the current state before changing access
Open the file’s Share dialog. Make a private note of its name, URL, owner, General access, direct people or groups, and the reason it is shared. Include the parent folder when permissions are inherited. Keep this audit log private because it can reveal internal file names and collaborators.
| Field | Example to replace with your own observation |
|---|---|
| File and owner | Project handoff notes; owned by me |
| General access | Anyone with the link — Viewer |
| Direct/inherited access | Project group; inherited from Client folder |
| Reason and decision | Public handoff finished; keep current project group |
| Verification | Public link denied in a signed-out window; team access checked |
| Review date | Record the actual date of your check |
Change an unnecessary link to Restricted
- Open the file, choose Share, and find General access.
- If Anyone with the link is no longer appropriate, select Restricted and save the change.
- Review People with access. A person or group with direct access may still be able to open the file after you restrict the link.
- Remove an outdated direct permission using its role menu when you are authorized to do so; save the change.
Use the least access that fits the current work: Viewer, Commenter, or Editor. Changing General access does not erase every other access path. Google’s stop-sharing instructions cover both link and individual access.
Handle inherited access and published copies
If Drive shows access inherited from a folder, inspect that parent folder before making a change. Under Google’s current sharing model, a file cannot simply give someone less access than they inherit from its parent. A folder change can affect other files, so review the folder’s purpose and collaborators before removing access.
For a team using shared drives, the shared-drive setup checklist explains how to record membership roles and item-level sharing. Review those routes together before treating a change to a single file link as complete.
Google Docs, Sheets, and Slides can also have a Publish to web setting. A published version is a separate exposure to review. Open the file in its editor, then choose File > Share > Publish to web > Published content & settings. Use Stop publishing when that published version is no longer intended. Restricting a Drive sharing link alone is not a substitute for that check. See Google’s publishing reference.
Verify the result with a small access test
Use a nonsensitive test file first if the workflow is unfamiliar. After changing General access, open the exact sharing URL in a signed-out browser window. A Restricted file should not open for someone without access. Then check the intended collaborators’ access using an authorized test account or their normal access verification process.
A signed-out denial only checks that route. A signed-in user may still have access through a group, folder, shared drive, or direct invitation. Record the route you actually tested. Permission changes also cannot recall screenshots, exports, or files that somebody already downloaded.
Common problems and what to inspect
- Restricted, but a colleague still opens it: inspect direct, group, and inherited access.
- You cannot remove a permission: check ownership, inherited folder access, and any organization policy.
- The file is still visible through a published page: check Publish to web in the editor.
- The search returns nothing: verify your account and query, then review known folders manually; empty search results do not prove nothing is shared.
Workspace administrators may have additional audit tools depending on their permissions and edition. This guide covers the files you can inspect in Drive and should not be treated as an organization-wide compliance audit.
For another inspectable Google Workspace rule, see Gmail receipt labels. Use a controlled status dropdown if you track review decisions in an Excel audit worksheet.

