Collect Client Files Without Sharing Your Folders

To collect client files without sharing a folder, send a file-request link or use a Google Form with a file-upload question. Both keep clients out of your folders, but Google Forms requires clients to sign in to a Google account before uploading.

A file-request link lets clients upload without seeing the folder

A file-request link is usually the simplest way to request files from clients without sharing a folder. You choose a destination folder in a service that supports file requests, then send clients a link made for uploading. The link is not a normal folder-sharing invitation. In Microsoft OneDrive file requests, for example, Microsoft says people using the request link can add files but cannot see what is already in the folder.

A file request works well when the client already knows what to send and you do not need a detailed questionnaire. Ask for the documents in your message, and tell the client how to identify their submission. A short, consistent file name helps your team match an upload to the right job, but do not put sensitive personal details in the name.

Check the settings before you send the link. Your organisation may restrict external sharing or disable file requests, and a link that works for a colleague may fail for an outside client. Also check whether anyone holding the link can use it. If so, send it directly to the intended client and close the request when collection is finished.

Google Forms uploads keep Drive private but require sign-in

A Google Form with a file-upload question lets clients submit files without seeing your Drive folders, but the client must sign in to a Google account to upload. That requirement can stop a client who does not have an account, cannot use one for work, or expected a quick upload without signing in.

Choose a form when you also need structured answers, such as a project name, document type or contact details. Add a file-upload question and set the file types and limits that fit the work. Google says uploaded files are stored in the form owner's Google Drive. The client interacts with the form, not with your Drive folder, unless you separately give them access.

Do not assume every client can open the form just because its link works for you. Review any settings that limit responses to people in your organisation. Then ask someone outside your organisation to try the form with the kind of account your clients actually use. If Google sign-in is an obstacle, switch to a file-request tool that permits external uploads without an account, subject to your organisation's settings.

The client sign-in test settles the choice

Choose a file-request link when a client needs to send files with as little friction as possible; choose Google Forms when the answers collected alongside each file matter more than avoiding Google sign-in. Neither choice should require giving the client access to your working folder. The deciding question is whether the intended client can complete the upload under the actual sign-in and sharing rules.

Run a small test before using either method for a real intake. Open the link outside your usual signed-in work session and, ideally, have a colleague with an external account try it. Check that they can submit a harmless sample file, cannot browse other submissions, and receive whatever confirmation the tool provides. On your side, check where the file lands and whether you can tell who sent it.

A private browsing window can reveal a sign-in prompt, but it cannot prove that every client's workplace permits the upload. If the test fails, identify which gate stopped it: Google account sign-in, a form restricted to your organisation, or your storage provider's external-sharing policy. Fix that gate rather than changing folder permissions to make the link work.

A safe file request has a clear destination and deadline

A client upload link should lead to a folder you control, with access limited to the people who need to handle the files. Create a separate intake location for the job or client rather than collecting unrelated submissions in a busy shared folder. Before sending the link, confirm that the receiving team can find the files and that clients cannot view each other's material.

Tell the client what to send, which formats are useful, and how to contact you if the upload fails. Avoid asking for more personal or confidential information than the work requires. If the documents are especially sensitive, check your organisation's approved storage and handling rules before choosing a form or file-request service. An upload-only link protects the folder from browsing; it does not, by itself, settle whether that service is appropriate for the documents.

Keep a record of which clients have submitted, separate from the files themselves. When the request is over, stop accepting uploads where the tool allows it and review access to the destination folder. Do not turn on broad folder sharing merely to help a late client submit.

The next handoff should not expose client submissions

After files arrive, notify the right person without forwarding the upload link as if it were a viewing link. A file-request link is for submissions; team members who need to review documents should use their own authorised access to the destination folder. That separation helps keep client access narrow while letting the work continue.

Start with a manual check if submissions are occasional. For a busier intake, a folder-based notification can alert your team when something new arrives. The guide to emailing your team about new files covers that next step. Check whether your chosen upload method places files where the notification watches before relying on it.

If you track outstanding requests in a spreadsheet, update the record only after confirming the file belongs to the expected client. A name typed into a form or attached to an upload is a clue, not proof of identity. For individual reminders, the guide to sending personalised Gmail messages from Sheets can help you prepare a careful follow-up. Keep client files out of reminder messages unless your organisation's process specifically calls for attachments.

Sources consulted

• Google Forms Help (support.google.com)
• Microsoft Support (support.microsoft.com)

Start a free course