Google Drive says You need access: how to send files in 2026

People screenshot You need access because it looks like the file is broken. It is not. Google Drive is doing what Restricted means: only named accounts get in. The client is on a phone, often in the wrong Google login, or in none. They tap Request access. You are asleep. The job waits.

Every generic blog then says: switch General access to Anyone with the link. That kills the screen. It also publishes the master to whoever forwards the URL. Spike is the third option. A page. A preview you treat. No Google account.

What the You need access screen actually is

Google's help centre uses that sentence for Docs, Sheets, Slides, and the rest of the Drive family. It means permission, not a corrupt file. Typical causes:

• The file is Restricted. Only emails you typed can open it.
• They are signed into a personal Gmail. You shared a work address.
• Gmail over 25 MB inserted a Drive link. That file was never public.
• Someone forwarded the URL to a producer who was never on the list.

Request access is an email to you. If you approve, they get another email. If you miss it, they think you ghosted them. That is not a delivery. It is a ticketing system wearing a folder.

Why Anyone with the link is a leak, not a fix

Anyone with the link is easy. It is also how a couple's gallery, a client's face, or a brand pack ends up in a group chat. Drive cannot blur a still. A full-resolution JPEG in that tree is a download. Viewer still downloads. You cannot put a price on it. You cannot sample three PDF pages and hold the rest.

Keep Drive for the workbench

Drive is still the right room for drafts, comments, and a team that already lives in Workspace. Do not move the studio out of Docs because a client hates Request access. Export the finals. Hand a door. How to share files with clients.

What to send so they never see that screen

1. 01

   Leave the working files in Drive

   Comments and versions can stay. The client does not need that tree.

2. 02

   Put the deliverable in one Spike folder

   The stills, the PDF, the cut. Treat the unpaid view if looking should not be taking.

3. 03

   Choose the door

   A normal share if the job is already paid. A password if the URL might be forwarded. Password protect a file share. Sell This Folder if they still owe you. Stripe, GBP, minimum £1.

4. 04

   Paste spike.zip/f/… where you would have pasted Drive

   Email, WhatsApp, Slack. They open a page. No Request access. No second Google login.

The wrong Google account problem

Google's own help says: if you have more than one account, sign into the one the file was shared with. Clients have a school login, a work login, and a personal Gmail. They tap the link from WhatsApp. Chrome is on the wrong profile. You need access again. A Spike page does not care which Google they are. It is not a Google file.

When Drive sharing is still right

• Both of you must comment in a Doc.
• The recipient already has the Workspace seat you named.
• The file is a sheet they must edit, not a pack they must take.

Those are workbench jobs. A wedding set is not. Dual-run: Drive inside the studio, Spike for the URL you send. The mistake is making the client a Viewer on a tree that also holds someone else's job.

You need access is Drive doing its job. It is a terrible client delivery.

Google Drive You need access in 2026 is a permission screen, not a broken file. Do not fix it by publishing the master to Anyone with the link. Keep Drive for the work. Put the pack on a page they can open without a Google account. What Spike is is that page: preview, optional password, optional checkout, no Request access.