[Link in Seconds](https://linkinseconds.com/) [Pricing](https://linkinseconds.com/pricing) [Log in](https://linkinseconds.com/login)[Sign up free](https://linkinseconds.com/signup) [All articles](https://linkinseconds.com/blog) # Google Drive link says “Request access”? 6 causes and the fix for each [Sunny](https://linkinseconds.com/about#who-runs-this)·September 4, 2026· 8 min read [#secure](https://linkinseconds.com/blog/topic/secure-sharing)#troubleshooting#google#drive#link Fix Drive 'request access' links contract.pdf Live lisview.com/shared You shared a file. They replied with a screenshot of **"You need access. Request access or switch to an account with access."** You open the link yourself, it works perfectly, and now you are both confused. The link is not broken. Google Drive is doing exactly what it was configured to do, and the configuration is usually one of six things. Here they are in the order they actually happen, with the fix for each, and the honest point at which it is faster to stop fighting Drive. The short answer - **Test it in an incognito window first.** The link works for you because you own the file. Incognito is the only view that tells you the truth. - **Most likely cause:** General access is still _Restricted_, or your recipient is signed into a different Google account than the one you shared with. - **If your Workspace blocks external sharing**, no setting fixes it. Send the file as a public link from somewhere outside that policy instead. In this guide - 1First: check it the way they see it - 2Cause 1: Access is still “Restricted” - 3Cause 2: Your domain blocks external sharing - 4Cause 3: They’re on the wrong Google account - 5Cause 4: The file moved, or its folder changed - 6Cause 5: An older file with a resource key - 7Cause 6: Too much traffic on one file - 8Which cause is yours? - 9The 60-second fix, in order - 10When to stop fixing Drive - 11Common questions ## First: check it the way they see it Before changing any setting, open a **private/incognito window** and paste the link there. You are signed into nothing, which is the closest thing to being your recipient. If it opens, your sharing is fine and the problem is on their side (cause 3 below). If you get the request-access screen too, the problem is the file's permissions (causes 1, 2, 4, 5). Do this before anything else One incognito check saves the usual round of "try now?" messages, and every fix below splits cleanly on its result. ## Cause 1: General access is still "Restricted" This is the default, and it is the single most common cause. Restricted means _only people I named can open this_, so the link itself grants nothing. **Fix:** open the file → **Share** → under **General access** change _Restricted_ to **Anyone with the link**, and set the role to _Viewer_ (or Commenter / Editor if you mean it). Copy the link from that dialog, not from the address bar. ## Cause 2: your organisation blocks sharing outside the domain On a Google Workspace account, an admin can turn off external sharing. When they have, the "Anyone with the link" option is missing, greyed out, or silently limited to people inside the company, so a link that looks public to you is still a wall for a client. **Fix:** ask an admin to allow external sharing for your unit, or move the file somewhere the policy does not apply. In a strict organisation the second is the only realistic answer, and it is the reason many people end up [sending client files from outside Drive](https://linkinseconds.com/google-drive-alternative) entirely. ## Cause 3: they are signed into the wrong Google account The quiet one. Anyone with a work and a personal Google account (or a family device with several profiles) opens your link as whichever account their browser considers _default_. You shared with their work email; the browser opens as their personal one; Drive correctly refuses. **Fix (their side), in order of reliability:** - Open the link in an incognito window and sign in with the exact address you shared with. - Or edit the URL: change the **/u/0/** segment to **/u/1/** (0 is the first signed-in account, 1 the second, and so on). - Or sign out of every Google account, then open the link and sign in with the right one. **Fix (your side):** ask which address they are actually signed in as and share with that one, or switch General access to "Anyone with the link" so which account they use stops mattering. ## Cause 4: the file moved, or its folder changed Drive permissions are inherited from the parent folder. Move the file into a folder shared with fewer people (or into a Shared Drive with its own membership) and its effective access changes without anyone touching the file. The link stays identical, which is what makes this so confusing to debug. **Fix:** re-open **Share** on the file in its new home and re-apply General access. Also check whether what you shared was a _shortcut_: a shortcut grants no access to the file it points at. ## Cause 5: an older file with a resource key In 2021 Google tightened link sharing on files created before that change. Those links carry a **resourcekey** parameter, and a link that had it stripped (pasted through a tool that trims query strings, forwarded in a client that shortens URLs) can hit the request-access screen even though sharing looks correct. **Fix:** copy a fresh link from Drive's **Share → Copy link** and send it as-is, or make a copy of the file (the copy is a modern file with no resource key). ## Cause 6: too much traffic on one file Drive is a drive, not a CDN. A file that suddenly gets thousands of opens (a link in a newsletter, a QR code on a poster, [an image hotlinked from a website](https://linkinseconds.com/image-to-link)) can hit a download quota and start refusing people for around 24 hours, with an error that looks a lot like an access problem. **Fix:** there is no setting for this. If a file is going to be opened by a crowd, it needs to be hosted rather than shared from a personal drive. ## Which cause is yours? | Tool | Works in your incognito window? | Typical tell | Fix | | Restricted accessCause 1 | No | Share dialog says “Restricted” | General access → Anyone with the link · Viewer | | Domain policyCause 2 | No | “Anyone with the link” is missing or greyed out | Ask an admin, or host the file outside Drive | | Wrong Google accountCause 3 | Yes | Only some recipients are blocked | Incognito, or /u/0/ → /u/1/, or share with their real address | | Moved file or shortcutCause 4 | No | It used to work and nobody changed sharing | Re-apply access in the new folder; don’t share shortcuts | | Old file, missing resource keyCause 5 | Sometimes | An old file, and the URL lost its ?resourcekey= | Copy a fresh link from Share, or duplicate the file | | Download quotaCause 6 | Sometimes | It broke right after the link got popular | Host it properly, Drive throttles crowds | Restricted access Cause 1 Works in your incognito window? No Typical tell Share dialog says “Restricted” Fix General access → Anyone with the link · Viewer Domain policy Cause 2 Works in your incognito window? No Typical tell “Anyone with the link” is missing or greyed out Fix Ask an admin, or host the file outside Drive Wrong Google account Cause 3 Works in your incognito window? Yes Typical tell Only some recipients are blocked Fix Incognito, or /u/0/ → /u/1/, or share with their real address Moved file or shortcut Cause 4 Works in your incognito window? No Typical tell It used to work and nobody changed sharing Fix Re-apply access in the new folder; don’t share shortcuts Old file, missing resource key Cause 5 Works in your incognito window? Sometimes Typical tell An old file, and the URL lost its ?resourcekey= Fix Copy a fresh link from Share, or duplicate the file Download quota Cause 6 Works in your incognito window? Sometimes Typical tell It broke right after the link got popular Fix Host it properly, Drive throttles crowds Six causes of “Request access”, and which one your incognito test points to. Behaviour checked against Google Drive's sharing model as of September 2026. Workspace admins can override any of it, so a policy in your organisation always wins over a setting on the file. ## The 60-second fix, in order - 1 Open the link in an incognito window Signed into nothing is the only honest test. It tells you which half of this list applies. - 2 Share → General access → Anyone with the link Set the role to Viewer unless you genuinely want comments or edits. - 3 Copy the link from that dialog Not from the browser address bar, that is how a resource key gets lost. - 4 Re-test in incognito, then send If it still asks for access, it is your organisation's policy (cause 2), and no setting on the file will beat it. The settings that actually decide it General access “Restricted” by default, the link grants nothing until you change it Role Viewer, Commenter or Editor. Viewer is right for anything you are just sending out Where to copy the link The Share dialog's Copy link button, never the address bar How to test it A private/incognito window, before you send What no setting can fix A Workspace policy blocking external sharing, and Drive's download quota Every Drive link asks a question: who are you, and are you allowed? For an internal doc that is the right question. For a menu, a proposal or an invoice, it is pure friction. ## When to stop fixing Drive and just send a link All six causes have the same root: Drive is a permissions system that happens to produce URLs. That is the right design for internal documents and exactly the wrong one for a menu, a portfolio, [a proposal or an invoice](https://linkinseconds.com/pdf-to-link-converter), or anything a stranger has to open on a phone. For those, a public link is a simpler object: it opens for whoever holds it, and there is no account behind the question. Upload the file (up to 250 MB free) and you get one clean URL, [a QR code](https://linkinseconds.com/qr-code-generator), and a view count: A public link asks nobody who they are, it just opens. And this is the whole experience on the other end, with no sign-in, no Drive UI, no folder: lisview.com/summer-menu What your recipient gets instead of a request-access screen. - No sign-in, so "request access" cannot happen. There is nothing to request. - No account-switching problem, because no account is involved on their end. - It opens in the browser: the PDF renders, the video plays, the image displays. - A view count tells you it landed, and a QR code covers anything printed. - You can still lock it down when it matters: a password, an expiry date or view-only, all free. The honest limits are in [what "secure" really means](https://linkinseconds.com/blog/share-files-securely-by-link). Keep both Drive is still the right home for the working folder your team edits all day, where permissions are the point. The two tools are not competing; [they answer different questions](https://linkinseconds.com/blog/wetransfer-vs-google-drive-vs-dropbox). ## Common questions ### Why does it work for me but not for them? Because you own the file, so Drive never has to check the link's public permission. Test every share link in an incognito window before you send it, that is the whole trick. ### Can I share a Drive file with someone who has no Google account? Only via "Anyone with the link". Sharing to a specific email always requires them to sign in, and some Workspace domains block external link sharing outright. ### Should I just click "Request access"? It works, but it costs a round trip: an email to the owner, a click, and a wait. If you are the owner and you are getting these requests repeatedly for the same file, that is the file telling you it should have been a public link. ### What about big files? Same answer, with an extra wrinkle: Drive counts against your 15 GB (shared with Gmail and Photos), and a big file still has to be fully downloaded before it can be read. A hosted link opens in the browser instead. See [sending a large PDF](https://linkinseconds.com/blog/send-a-large-pdf) and [sending a video too big for email](https://linkinseconds.com/blog/video-too-big-for-email). The short version Check the link in an incognito window, set General access to **Anyone with the link · Viewer**, and confirm which Google account your reader is actually signed into. If your organisation blocks external sharing (or the file is going out to people you will never manage), [send a public link instead](https://linkinseconds.com/share-files-online) and the question never comes up again. Try it while you are reading Upload a file and get a clean, trackable link with a QR code. Free, and no account for whoever opens it. [Create a link](https://linkinseconds.com/) ## Keep reading - [Do Google Drive links expire? brief.pdf Live lisview.com/shared Do Google Drive links expire? How long a Drive link lasts, and what actually ends it 6 min read](https://linkinseconds.com/blog/how-long-does-a-google-drive-link-last) - [5 views, 1 reader bots · previews · scanners quote.pdf Live lisview.com/quote Why your file views look too high: bots, link previews and email scanners explained 6 min read](https://linkinseconds.com/blog/why-your-file-views-look-too-high) - [Share files securely by link contract.pdf Live lisview.com/secure How to share files securely by link, and what “secure” really means 7 min read](https://linkinseconds.com/blog/share-files-securely-by-link) ## Turn any file into a link in seconds Upload a PDF, image, video, or ZIP and get a clean, trackable link with a QR code, free. [Try Link in Seconds →](https://linkinseconds.com/) [Link in Seconds](https://linkinseconds.com/) Turn photos, PDFs and files into one clean link to share, with view tracking and a QR code. Works in the browser, nothing to install. [Follow on LinkedIn](https://www.linkedin.com/company/linkinseconds)[Instagram](https://www.instagram.com/linkinseconds/)[YouTube](https://www.youtube.com/@linkinsecondsapp) Featured on 33, Bhaktinandan, Sector 4, S G Road, Mota Varachha, Surat, Gujarat 394101, India [+91 99090 97776](tel:+919909097776) [support@linkinseconds.com](mailto:support@linkinseconds.com) Secured by Dodo PaymentsVisaMastercard Use cases - [Wedding photos](https://linkinseconds.com/wedding) - [Event photos](https://linkinseconds.com/event-photo-sharing) - [Family photos](https://linkinseconds.com/share-photos-with-family) - [Client proofs](https://linkinseconds.com/client-photo-proofs) - [Property listings](https://linkinseconds.com/property-listing-link) - [Product catalogue](https://linkinseconds.com/product-catalogue-link) - [Pitch decks](https://linkinseconds.com/share-pitch-deck) - [Resume link](https://linkinseconds.com/resume-link) - [Portfolio link](https://linkinseconds.com/portfolio-link) - [Class photos](https://linkinseconds.com/class-photos) - [All use cases](https://linkinseconds.com/use-cases) Tools - [Image to link](https://linkinseconds.com/image-to-link) - [PDF to link](https://linkinseconds.com/pdf-to-link-converter) - [Video to link](https://linkinseconds.com/video-to-link) - [Share files online](https://linkinseconds.com/share-files-online) - [QR code generator](https://linkinseconds.com/qr-code-generator) - [Large files by email](https://linkinseconds.com/send-large-files-via-email) - [View-only sharing](https://linkinseconds.com/view-only-file-sharing) - [Menu QR code](https://linkinseconds.com/pdf-menu-qr-code) - [Proposal tracking](https://linkinseconds.com/proposal-tracking) - [All file viewers](https://linkinseconds.com/viewer) PDF tools - [Merge PDF](https://linkinseconds.com/merge-pdf) - [Split PDF](https://linkinseconds.com/split-pdf) - [Rotate PDF](https://linkinseconds.com/rotate-pdf) - [Organise PDF](https://linkinseconds.com/organize-pdf) - [Watermark PDF](https://linkinseconds.com/watermark-pdf) - [JPG to PDF](https://linkinseconds.com/jpg-to-pdf) - [PDF to JPG](https://linkinseconds.com/pdf-to-jpg) - [All PDF tools](https://linkinseconds.com/pdf-tools) Hosting - [Host a static site](https://linkinseconds.com/host-static-website) - [HTML hosting](https://linkinseconds.com/html-hosting) - [Publish an HTML ZIP](https://linkinseconds.com/publish-html-zip) - [Host AI-generated HTML](https://linkinseconds.com/host-ai-generated-html) - [Deploy a Vite build](https://linkinseconds.com/deploy-vite-react-build) - [Publish from AI (MCP)](https://linkinseconds.com/docs/mcp) - [File upload API](https://linkinseconds.com/docs/api/uploads) Compare - [vs WeTransfer](https://linkinseconds.com/wetransfer-alternative) - [vs Dropbox](https://linkinseconds.com/dropbox-alternative) - [vs Google Drive](https://linkinseconds.com/google-drive-alternative) - [vs Tiiny Host](https://linkinseconds.com/tiiny-host-alternative) - [vs DocSend](https://linkinseconds.com/docsend-alternative) - [vs Google Photos](https://linkinseconds.com/google-photos-alternative) - [vs Pixieset](https://linkinseconds.com/pixieset-alternative) - [vs Netlify Drop](https://linkinseconds.com/netlify-drop-alternative) - [vs Smash](https://linkinseconds.com/smash-alternative) - [vs Issuu](https://linkinseconds.com/issuu-alternative) Company - [Pricing](https://linkinseconds.com/pricing) - [Blog](https://linkinseconds.com/blog) - [FAQ](https://linkinseconds.com/faq) - [About](https://linkinseconds.com/about) - [Contact](https://linkinseconds.com/contact) - [Contact sales](https://linkinseconds.com/contact-sales) - [Docs](https://linkinseconds.com/docs) - [API & MCP](https://linkinseconds.com/docs/developers) Legal - [Terms](https://linkinseconds.com/terms) - [Privacy](https://linkinseconds.com/privacy) - [Cookies](https://linkinseconds.com/cookies) - [Refunds](https://linkinseconds.com/refunds) - [Acceptable use](https://linkinseconds.com/acceptable-use) - [Copyright](https://linkinseconds.com/dmca) - [Report abuse](https://linkinseconds.com/abuse) - [Child safety](https://linkinseconds.com/child-safety) - [Grievance](https://linkinseconds.com/grievance) - [Trust and safety](https://linkinseconds.com/trust) - [Security](https://linkinseconds.com/security) - [Legal notice](https://linkinseconds.com/legal-notice) © 2026 Link in Seconds. All rights reserved. [Terms](https://linkinseconds.com/terms)[Privacy](https://linkinseconds.com/privacy)[Cookies](https://linkinseconds.com/cookies) Source: https://linkinseconds.com/blog/google-drive-link-request-access