Share a Gemini-assisted document without sharing more than you meant to
Your summary may contain a sentence from a file its new readers were never meant to see. It has no numbers in it, and nobody decided to write it.
What you'll make
a checked sharing copy of a Gemini-assisted Google Doc, sent to the people you meant with the least access they need.
What you'll need
Gemini in a Google Workspace account, the draft and the sources it drew on, the right to share the final content and to change the file’s sharing settings, and about fifteen minutes.
Example result.
Sharing copy: "All four depots met the delivery target. November training is proposed, subject to approval."
Removed: supplier renewal-rate sentence (restricted review; owner asked); unsourced fuel-cost claim.
Access: Restricted; Operations team group as Commenter; folder checked for wider access.Here’s the leak you’re guarding against. Access is checked at your account, not the reader’s. Gemini reads a restricted file you can legitimately open, writes two sentences summarising it into a Doc, and those sentences now live in a file whose sharing has nothing to do with the original’s. The permissions did their job. The content walked out anyway, inside a different document, with your name on it.
1. Name the audience and gather the sources
Write down who should receive the document and why. A team update, a supplier briefing and a public page need different content, even from the same notes.
Then list what went into the draft. Select Sources below a Gemini response to see the files it used, but don’t rely on that list alone: Google says it can be incomplete or wrong, and sources added earlier stay active for the whole conversation. If you started from Drive, check the search settings too: there, Drive, Gmail, Chat and Calendar search are on by default for a new conversation.
Why this works: you can only check a sentence against its source if you know every source that was in play.
What you should see: a named audience and a list of every file or extract that could have fed the draft.
2. Map the risky passages to their sources
Review this draft for [audience and purpose]. Using only the draft and the sources, identify passages that contain information from [restricted sources]. Give each draft passage and the source passage or location behind it. Flag any fact whose source you can't establish. Do not invent a source. Do not decide what I'm allowed to share, change permissions or send anything.[audience and purpose] is your line from step 1; [restricted sources] names the files whose content is limited.
Why this works: a file list tells you what was in the room. A mapping tells you which paragraph is the problem.
What you should see: passages paired with their sources, and a list of facts with no source. Check each pairing yourself, and read the passages it didn’t flag too.
3. Make a clean sharing copy
Keep the working draft separate and make the recipients’ copy from the material that’s cleared for them. Read the whole thing: body, tables, links, comments, images. A clean first paragraph doesn’t fix a revealing table at the end, and a link can expose a source’s title even if the recipient can’t open it.
If a sentence needs the owner’s say-so, ask before sending. Don’t ask the model to infer permission from the importance of your deadline.
Why this works: the recipient sees the whole file, so the check covers the whole file.
What you should see: a copy with every restricted or unsourced passage removed or rewritten, and nothing internal in comments or links.
4. Set the access in the Share dialog
Open Share and look at two separate parts:
- Specific people: the names and groups with access. Add recipients with the least useful role: Viewer to read, Commenter for feedback, Editor only if they’re changing the document (editors can also share it and change permissions). On an eligible work account, Add expiration sets an end date, which is the right default for a contractor or a one-off review.
- General access: the dropdown below, and the one that catches people. Restricted means only the people listed. Anyone with the link means anyone holding the URL. For a document with content from a restricted source, that isn’t a convenience setting; it’s a publication decision.
Check the containing folder too. Access set on a folder applies to every file inside it, and you can’t give someone less access to one file than they have on the folder. Download, print and copy settings for viewers sit under the Settings gear in Share; they don’t stop someone retyping what they can read.
Why this works: content and access are separate checks, and a narrow role doesn’t make a restricted sentence safe.
What you should see: Restricted, the named people or group at the right role, and no wider access inherited from the folder.
Check the result
- Every sentence in the sharing copy traces to a source cleared for this audience.
- Facts with no source have been removed or sourced.
- General access is Restricted unless a wider audience is intended.
- The folder doesn’t give anyone more access than you meant.
The usual failure: one sentence from a restricted source survives because it looks harmless: no figures, no names, just “rates will rise at renewal”. Spot it by checking every sentence about money, suppliers, people or plans against the source mapping from step 2.
Rewrite this passage for [audience] using only these cleared facts: [cleared facts]. Do not include [excluded information] or hint at it. If the remaining facts don't support a useful sentence, recommend removing the passage. Do not invent a replacement explanation.[cleared facts] are what the audience may see; [excluded information] is what must stay out. Read the result for indirect hints.
Worked example: a quarterly team summary
Fictional example. An operations lead drafts an update for a team of thirty from a performance sheet, a planning document and a commercial review shared with four people.
Draft passage:
"All four depots met the delivery target. Training is planned for November. Our supplier's unit rate will rise at renewal. Industry fuel costs have also increased."
Known sources:
Performance sheet: all four depots met the stated target.
Planning document: November training is proposed, subject to approval.
Restricted commercial review: supplier renewal-rate discussion.
No source supplied for the fuel-cost claim.- The failure. The third sentence has no numbers and was written without anyone deciding to write it. It tells thirty people something four were trusted with, and it would reach the supplier’s account manager within the week.
- The repair. The mapping prompt flagged it against the commercial review. The lead cut it and asked the review’s owner what could be said; the answer was nothing yet. Training became “proposed, subject to approval”, and the unsourced fuel claim went. That gives the copy in the example result.
- The access. She shared it with the team group as Commenter, with Restricted general access, and checked the folder. Commenter wouldn’t have made the commercial sentence safe; the content review came first. Asking the owner took thirty seconds before sending, against a much longer conversation afterwards.
Task kit for this job: Download (ZIP) · Reusable instructions
Go deeper
Optional training: Narrow the sources before drafting
For a widely shared document, start Gemini with only audience-appropriate sources. In Docs, Gmail and Slides, open Ask Gemini, then Add sources › Gemini search settings, and switch off Drive search, Gmail search, Chat search or Web search as needed. In Drive, the left panel’s Let Gemini search for sources lets you uncheck Drive, Chat, Calendar, Gmail or Web. Sources stay active for a whole conversation, so start a new one if an earlier turn used material you now want to exclude. These choices reduce what’s in play; they don’t replace the review of the final copy.
Optional training: Keep a short approval record
Document and intended audience:
Sources reviewed:
Passages removed or changed:
Content approval still needed:
Approval received from / date / scope:
Recipients or group checked:
Role and general access:
Folder access checked:
Final copy checked by / date:Keep it with the working material, not in the recipients’ copy. Record only approvals you actually received. “I assume they would be fine with it” doesn’t fill the approval field. For handing over a result from a chat rather than a Doc, see Share an AI result without sharing the whole conversation.