Google Drive Sharing: Give Clients Access to the Right Files

For a proposal intended for one client, start by sharing the file with the email address they use for Google collaboration. Keep general access restricted and give them the role required for the review. A request for access does not, by itself, call for making the document available to anyone with its link.

Suppose your project folder contains a proposal, an internal costing sheet, and meeting notes. Giving a client the whole folder to fix a problem with the proposal would also expose the other documents. The steps below cover Drive in a desktop browser, with separate conditions for organization-owned shared drives.

Invite the recipient to the file

Select the proposal in Drive and open Share. Under general access, keep the file restricted, add the recipient's email address, choose their role, and send the invitation with notifications enabled. You can then copy that file's link into the email containing your review instructions. Google's sharing guide describes both named invitations and broader link access.

An invitation identifies who may use the file; a copied link identifies the file to open. Include the intended task in your message: for example, ask the client to comment on the delivery dates by the agreed review deadline. They should not need to guess whether they are reviewing a finished document or editing a working draft.

A restricted link forwarded to another reviewer does not automatically grant that person access. An anyone-with-the-link setting allows a wider audience to open it without signing in. That may suit a product brochure meant to circulate freely. For a customer-specific proposal, ask the client to identify additional reviewers so you can invite them deliberately.

When an invited client still needs access

Compare the email in your sharing dialog with the account the client is using. People can be signed in to personal and work accounts simultaneously. One support question describes a shared link opening under the wrong account, with switching accounts returning the user to Drive's home screen.

Ask the recipient to select the invited account and reopen the original document link. Google's access troubleshooting guidance explicitly includes checking for a different signed-in account. Returning to the home screen does not prove the invitation has disappeared.

If you invited a company address but receive an access request from a personal address, establish which identity should receive the proposal before approving it. Otherwise, a login mismatch becomes an additional permission you must manage later. If the intended account genuinely lacks access, the owner needs to grant it; submitting a request is not an approval.

For a useful follow-up, have the client send the account address and the exact error shown. “The link is broken” could describe a missing permission or an organization restriction, and resending the same URL will not change either setting.

Match permissions to the review

A final proposal, a draft awaiting comments, and a jointly maintained schedule call for different actions. For a proposal written in Google Docs, the roles work as follows. Commenting features and their interfaces can vary for other file formats.

Viewing does not inherently prohibit downloading. Google's sharing guide describes Viewer, Commenter, and Editor roles under “Understand access levels and roles,” with separate settings under “Prevent downloading or copying.” A client may need to save the final PDF for an internal approval process while having no reason to edit your original.

Agree on that deliverable before disabling downloads. For online-only review, the owner can open Settings from the sharing dialog and adjust the role checkboxes for download, copy, and print access. If saving a PDF is part of acceptance, leave the necessary download access enabled. Ask the client to save the file they need for approval, not merely confirm that its preview opens.

Restrictions may also come from the organization. In Docs, Sheets, Slides, and Vids, the security limitations view identifies restricted actions and the source of those controls. Raising a client to Editor is not a reliable remedy for a blocked download.

Keep internal files out of the handoff

Folder access carries through to its contents. A person who receives access through the parent cannot simply be assigned less access on an ordinary child file. If someone can still open the proposal after you remove a direct invitation, inspect the parent folder and any relevant group membership.

For a new project, a practical arrangement is a client-delivery folder containing only the proposal and approved supporting material. Keep your costing sheet and internal notes outside it. When a revised schedule is approved for the client, add it beside the proposal. Keep the team's discussion of possible delays with the internal notes until you have an agreed update to send.

Where an existing hierarchy needs an exception, use a limited-access folder. Open its sharing settings in Drive on the web, enable the access limit, then manage the permitted users. Owners can do this in My Drive; shared-drive Managers can do it in a shared drive. My Drive editors need permission to change sharing settings.

Limited access does not always conceal the folder's existence: other parent-folder users may see a grayed-out name. Also check general access and groups, which can leave another route in. For material that has no place in the client's workspace, a separate internal location is easier to explain and maintain.

On an organization's shared drive, consider sharing the individual file with a non-member instead of adding the client as a drive member. Google's shared-drive access guidance describes that option, subject to the drive's external-sharing and non-member restrictions.

Clients without Google accounts and external restrictions

A non-Gmail address can still belong to a Google account. Google supports creating an account with an existing email address. Ask whether the client already signs in with their company address before asking them to create another identity.

For recipients without Google accounts, organizations that enable visitor sharing can use email verification. The recipient opens the invitation and enters a PIN sent by email. Verification allows collaboration for seven days; continued use requires verification again through the original invitation. This interval is not a permanent expiration of the shared document.

Keep the invitation addressed to the person doing the review. If a colleague takes over, invite that colleague rather than treating a forwarded verification message as the handoff. Each reviewer then has an identifiable access path that can be removed when their work ends.

Your organization may block external sharing or allow only trusted domains. Those Workspace policies can prevent an otherwise appropriate invitation. Send the administrator the file link, recipient address, error, and requested task. They can assess whether the recipient and collaboration method are permitted; repeatedly changing the file's role will not remove the policy.

Test the handoff and close access afterward

Opening your own link tests your access, not the client's. Have the recipient open it using the invited account and perform the agreed action, such as leaving a comment or saving the final PDF. A signed-out browser is useful for checking a public brochure link. It should fail to open a file intended only for named users.

When collaboration ends, remove the client from the proposal's sharing dialog and save. If you enabled broad link access, restrict that too. If the client can still open the file, check whether a group they belong to or a shared parent folder provides access. Work with whoever manages that group or folder to remove the client's access without interrupting colleagues who still need the document. Keep the working proposal for the team.

A temporary external-sharing block on a shared drive can leave permissions in place. Google notes that previously authorized external users may regain access when the restriction is lifted. For a completed engagement, remove the client's grants rather than relying on the current organizational block.

Revoking access does not retrieve a proposal the client already downloaded.