Google Drive / Troubleshooting

Google Drive shared file won’t open: check the account before changing permissions

Separate a wrong-account problem from missing permission, download restrictions, and an organization’s sharing policy.

Documentation reviewed · Not hands-on tested
Quick answer

Check which email address is signed in before sending another access request. A client may have shared a file with your work address while your browser opens it under a personal account. Record whether the failure happens when opening the file, editing it, or downloading it; those are different permission questions.

In this guide
Applies to

Google Drive in a desktop browser; personal Google Accounts and Google Workspace work or school accounts. My Drive roles are discussed separately from organization policies. This is an access diagnosis, not file recovery.

Start with the account and the exact message

Keep the original link for comparison. If a collaborator sends a second link, label the two links rather than assuming they point to the same file. This makes it easier to establish whether you are troubleshooting the document the client intended to share.

If the page asks for access

Use the Google Account that the owner invited. If that account still cannot open the file, use the page’s access-request option and explain the work you need to do. The request identifies your signed-in account to the owner, so check that address first. Google’s file-access guide describes this process.

For example, a freelance editor who only needs to read a brief should request viewing access. Asking for editing access adds an unnecessary decision for the client. Include the file link and the intended recipient address in your message so the owner can compare them directly.

If the owner says it is already shared

Ask the owner to inspect that specific file’s sharing settings and confirm the recipient and role. In My Drive, viewing, commenting, and editing are separate roles. Google also documents that access granted through a parent folder carries into its files. The owner should therefore check the relevant folder when the file’s controls point there. See Google’s sharing documentation.

Avoid making a confidential folder public just to test whether the link works. A targeted invitation gives a more useful result without widening access to unrelated project material.

If you can read it but cannot download it

Opening the file successfully changes the diagnosis. For supported Google editors, the security-limitations view can distinguish a file-level restriction from an organization policy. Downloading or sharing may be restricted even when reading works. Google explains these distinctions in security limitations.

Ask for the operation you need, such as downloading an approved delivery copy. Do not describe this as a broken link or repeatedly request permission you already have.

When a work or school policy is involved

An organization may prohibit sharing with your account even when the owner wants to approve it. Have the owner ask their Workspace administrator about an approved handoff method. Moving the file to a personal account is not an appropriate diagnostic step for client-confidential work.

If the cause remains unclear, use the help or contact options on Google’s file-access guide. Provide the exact message, the affected operation, and the account type. Remove private document content from any screenshots you share.

Sources and review date

Official documentation consulted on 2026-09-20. Diagnostic suggestions are editorial guidance, not a promise of a particular result.

A step no longer matches your app? Report a correction with the guide URL and version you use.

Related fixes