Removed someone from Google Drive, but they still have access?

If someone can still open a Google Drive file after you remove them, another permission may be keeping it open. Check their direct invitation, group access, the containing folder, and any shared-drive membership. Also close general link access if it is no longer wanted. For a Google Doc, Sheet, or Slide, check a separately published web page too.

Start with the exact URL the person opened. A working document, its published page, and somebody’s saved copy can need different fixes. Changing the wrong item’s permissions will leave the reported problem untouched.

Remove the direct invitation and close the link route

If you own the item or can manage its sharing, open Share. Find the person, open the dropdown beside their role, choose Remove access, and save. Under General access, change Anyone with the link to Restricted and select Done if link-only readers should lose access. Google’s removal instructions

Then inspect the remaining permissions. A group or parent-folder grant can still supply access after the person’s individual invitation disappears. Restricted describes the general-access setting; it does not establish that every named collaborator has been removed.

Copying the link again will not produce a newly secured address. Drive keeps a file link based on the file’s identity and evaluates its permissions when a reader opens it. If another grant survives, the old URL can still work. Drive’s permission model

Follow five changes to the same file

Consider a fictional workshop file, sample-review.docx. Alex has four access routes: direct Editor, Viewer through reading-group, Editor through the Workshop parent folder, and Viewer through Anyone with the link. The owner should keep access throughout.

Stage	Alex’s effective role	What remains
Before changing anything	Editor	Direct, group, parent and link grants
Remove the direct invitation	Editor	Parent Editor, group Viewer and link Viewer
Change General access to Restricted	Editor	Parent Editor and group Viewer
Remove reading-group from the file	Editor	Parent Editor
Remove the originating parent grant	Denied	None of the four modeled routes

Download the five-stage trace. This is a synthetic teaching example, not a live account trial. The final Denied result assumes the four listed routes are the only grants. It does not measure Google’s processing time or confirm anyone’s real account.

The first removal succeeds at its own task: it deletes Alex’s direct permission. It leaves the Workshop folder’s Editor grant in place. Closing the link then affects readers using that general route, while Alex still has the named folder route. Removing the group grant is another real change, but Alex continues as a folder editor. The result changes only when the last applicable route is removed.

In a real workshop, Alex might still need a schedule or a presentation in the same folder. Do not apply the final row blindly to the entire Workshop folder. First decide which other items Alex should retain, then make the access change at the appropriate location.

Find the group permission behind the missing name

A file’s access list may show reading-group without listing Alex individually. Removing Alex’s separate invitation leaves that group route intact. Ask the relevant group manager whether Alex’s membership supplies this file’s access; a full roster or a screenshot of unrelated members is unnecessary. Google documents that group members receive the group’s permissions. Group sharing rules

The practical choice depends on whose access should end. If the whole group should lose this file, remove the group’s grant from this item. If Alex should leave the project entirely, a group manager can handle membership according to the project’s actual scope. If only this document should be private from Alex, removing Alex from an organization-wide group could disrupt unrelated work. Consider an appropriately configured limited folder for the exception.

Record which change you made. “Alex removed” is ambiguous if you removed a direct invitation but kept the group grant. “Direct Editor removed; reading-group still grants Viewer” describes the result someone else can troubleshoot.

Inspect the parent before changing its audience

An inherited permission originates above the file. Changing a direct invitation on the child cannot simply reduce the role supplied by its parent. In the example, the relevant grant is Alex’s Editor permission on Workshop. Permission inheritance

Open the containing folder’s sharing settings and identify that route. Before removing or reducing it, examine the sibling items the person should continue using. A folder-level change can affect more than the file that triggered the complaint. Record the folder’s name with the grant, rather than attributing the permission to the child alone.

When one file needs a narrower audience inside a shared folder, the manual limited-access setting applies to a subfolder, not directly to the file. Place the exceptional item in a suitable folder only after checking its destination and existing grants. The My Drive owner retains access. A permitted group or general-access grant can still let someone in despite an Access removed entry. Limited-access folders

For Alex, the useful question is whether the parent should stop granting access to all of Workshop or whether this document needs a separate boundary. Moving the file without understanding the destination can substitute one unintended audience for another.

Separate shared-drive membership from a file invitation

A person may be a member of a shared drive, or a non-member invited to one of its items. Removing a non-member’s direct invitation is narrower than changing drive membership. A member can still have the drive’s access route after a file invitation disappears. Drive-wide restrictions can also override item settings. Shared-drive access

A Manager handles drive membership and can toggle limited access. A Content Manager is a different role: permission to manage some item sharing does not make that person a Manager. Managers retain access to limited folders. Limited-access roles

If the disputed grant originates in membership, involve the appropriate Manager. Name the drive and item, and explain whether access should end for one document or the whole drive. That gives the Manager a specific scope to inspect without removing membership unnecessarily.

Check whether the URL is a published page

For a Google Doc, Sheet, or Slide published through File > Share > Publish to web, collaborator permissions and the published output are separate controls. To withdraw the published page, reopen Publish to web, expand Published content & settings, and use Stop publishing. The published audience depends on account policy. Publishing controls

This branch applies to those Google editor file types, not automatically to every PDF or uploaded Word file. Compare the recipient’s URL with the original file and any published URL before treating it as a permissions failure. A different file may be a copy, and changing your original does not change that copy’s permissions.

Previously downloaded material remains a separate problem: access removal cannot recall it. Deleting a file you do not own from your own Drive view also leaves other collaborators’ access intact. Google’s sharing and deletion explanation

Confirm the result with the affected identity

The owner opening the file proves nothing about Alex’s access. Ask a cooperative former recipient to open the same original URL using the identity that previously received access. Have a colleague who should retain access confirm that their needed file still opens. A signed-out check can reveal an anonymous link route, but cannot test Alex’s named or group permission.

Do not request a password or the document’s contents. The relevant details are the URL, the account identity used, and the observed access result. If you cannot obtain that check, record it as unconfirmed instead of treating your own successful view as proof of revocation.

The editable access audit contains four fictional route entries: direct, group, parent and general link. Replace them with your own item and grant locations, record the wider effect of each proposed change, and leave the recipient-check field unconfirmed until it actually happens.

A removal email is not proof that access ended. If collaborators need an operational notice, an owner could send a note such as this example; no message was sent for this article:

Access to sample-review.docx ended on 7 October. Open the original Drive link using the address that received it to confirm the change. If you still need a project file, reply with its name; do not attach a copy of the withdrawn document.

If that exact original URL still opens, identify the surviving grant and where it originates. If the reader is opening a published page or a different copy, deal with that object instead of repeatedly removing the same invitation.