How to check who can still open a shared Google Drive file

A useful Google Drive sharing check starts with a list of who should still have the document. Compare that list with the file's individual permissions, its general link setting and the folder around it. Changing one of those controls is only one part of the job.
Do the review in a desktop browser, using the account responsible for the file. Before changing anything, identify the exact document and the people who still need it. A draft budget and a final budget can have similar names but very different audiences. Record the file link, owner, intended readers and reason for the review in a private note.
Separate people from the link
Open the file's sharing dialog. Google's Drive help distinguishes named access from general access: Restricted limits the link to people already permitted to use the item. It does not turn your intended audience into an empty list.
Compare each listed person or group with your note. Remove an unnecessary individual invitation using the role menu and save the change. Then examine general access separately. If the document should no longer be available broadly through a link, choose Restricted. Review both sections again after saving.
Keep the decision specific. A colleague who only needs to read a finished document may require a different arrangement from someone still responsible for editing it. Avoid removing everyone as a shortcut if a live project depends on the file.
Follow access back to the folder
If the result still looks wrong, examine the parent folder and any group shown in the sharing dialog. Google's Workspace guidance explains that folder permissions pass down to their contents. A file-level change therefore may not resolve a permission granted higher up.
Decide whether the person should lose access to the whole project or only this document. Those are different changes with different consequences. Check the folder's other contents before altering its audience. If you do not control the relevant permission, ask the owner or administrator to make the specific change.
Google's >limited-access folder guidance (opens in a new tab) describes another option for sensitive material. It also warns that general access or membership in an allowed group can still provide entry. Treat a limited-access folder as another setting to check, not proof that every route has closed.
Test the boundary you meant to change
Reopen sharing and compare the saved settings with your intended-reader list. A signed-out browser test can check public link access. It cannot prove that a particular signed-in person has lost an invitation or group permission. For that, arrange a test with an authorized colleague using the relevant account. Do not request their password.
Write down what you tested and the result. For example: public link refused, intended editor still able to work, former direct invitation removed. These separate observations are more useful than a blanket note saying secure.
Account for copies already outside Drive
Google's sharing guidance cautions that its controls cannot prevent every other way of sharing content. Removing access should not be described as recalling files someone already downloaded, photographed or copied elsewhere.
If sensitive information was exposed, tell the responsible person what was shared, with whom and for how long. Preserve the relevant details before making further changes. For routine project closure, assign a person to review the remaining permissions and set a future review date. A short, repeatable check is easier to maintain than relying on memory when the next collaboration ends.


