A file in the bin can still be accessible

Ask what the request is meant to achieve

A colleague asks you to remove a document from Google Drive. Our recommendation is to clarify the intended outcome before acting: are they tidying their own view, retiring a working copy or asking for someone’s access to end? Write that outcome into the support request. Those aims need different evidence of completion.

Google says that when a file owner puts a file in the bin, other people can continue accessing it until it is permanently deleted. It also says that when someone who is not the owner removes a file, other people can still access it even if that person empties their bin. A file disappearing from one person’s view is therefore insufficient evidence that access has ended.

Identify the file and the responsible owner

Our suggested check records the exact file link and asks the business owner what should happen to the document. Avoid relying on the title alone when there may be several copies. Keep sensitive document contents out of the support ticket; record the decision and the authorised action instead.

In a fictional consultancy, a coordinator removes an old project document from their view and assumes a former collaborator can no longer open it. The project owner asks IT to review the access requirement separately. This is an illustrative misunderstanding, not a claim about a customer we have supported.

If the request is to end access, use the organisation’s approved access-review process and have an authorised person confirm the outcome. This article explains why deletion is not evidence of that outcome; it does not provide a complete access-removal procedure or promise that every existing copy can be recalled.

Do not use permanent deletion as a shortcut

Google says files remain in the bin for 30 days before permanent deletion, and manually emptying the bin permanently deletes them sooner. That product behaviour is not your organisation’s retention decision. Ask the document owner to resolve any requirement to keep the material before approving destructive cleanup.

Our advice is to keep an access concern and a disposal decision as separate actions in the ticket. Where a security incident is suspected, follow the established incident process rather than improvising a cleanup. Do not empty the bin simply to make the request appear complete.

For a harmless demonstration, use a disposable sample file and approved test accounts. Have the responsible administrator explain what the observed result establishes. Do not experiment with customer documents or deliberately widen sharing for the demonstration.

Close against the original outcome

Ask the requester and owner to confirm the result they needed. Record whether the task was a personal-view cleanup, an access review or an authorised disposal, and identify any action still outstanding. A screenshot of an empty folder should not stand in for that decision.

The useful handover is a short record that another support colleague can understand: which file was involved, what the owner authorised and how the intended outcome was checked. If the evidence does not answer the original request, leave that part open.