After exporting a Gemini answer to Docs, check who can open it before you hit Share

You export a Gemini-drafted project memo with "Export to Docs", the document opens, and your cursor goes to the Share button. Then you stall. It looks like any other doc, but you can't say who else can open it.

Rereading Google's help page explained why. It documents the steps and says a new document is saved in Drive. It says nothing about the file's owner or its starting sharing state. I had been filling that gap with "probably just me", which is a guess, not a fact.

Right after exporting, I check who can open the file before I decide who should. That one rule is what the rest of this piece unpacks: three places to look, what changes when you move the file, and a small audit for when the exports multiply.

What the help page says, and what it leaves out

The Gemini Apps help page "Export responses from Gemini Apps" lists each destination. The sharing-relevant parts:

For work and school accounts, the page also notes that export options depend on availability and Workspace settings. So the same click may behave differently for your colleague.

The Replit row is a useful reminder that "export" can mean "leave the building". It isn't about Docs, but it shows why I don't assume.

Three places to look right after exporting

Before choosing anyone to share with, go through these in order:

1. "General access" in the Share dialog. Is it Restricted, or has it become "Anyone with the link" or your whole organization?
2. Where the file lives. Which folder is it in? The next section explains why this matters.
3. People already added. Does the list at the top of the dialog contain anyone besides you?

Each takes about ten seconds. The order matters because a file can be Restricted and still be reachable through its folder.

Moving it into a shared folder brings the permissions along

Google Drive's help page on sharing folders says permissions from a parent folder are inherited by everything inside it, and that files added later inherit them too. It also says a file in a shared folder has the same or higher permissions than the folder itself.

Combine that with an export and the trap is easy to see:

• Right after exporting, the doc may be visible only to you (the help page doesn't say, so I don't assume).
• You tidy up by dragging it into the team's shared folder.
• Everyone who can see that folder can now open your draft.

If the memo mentions a client's name or an unannounced figure, its audience just grew without you pressing Share. So I look at the same three places before moving a file, and I find out the destination folder's audience first.

When exports pile up, audit them with Apps Script

As an indie developer who keeps exporting notes into Docs, I stopped being able to track by eye which ones I'd shared. Past about ten documents, a list is faster.

DriveApp exposes the sharing state of a file. Here is a minimal example that prints one line per document ID:

function listSharingState() {
  // IDs of the docs you want to check (the string between /d/ and /edit in the URL)
  const ids = ['YOUR_DOC_ID_1', 'YOUR_DOC_ID_2'];
  ids.forEach(function (id) {
    const f = DriveApp.getFileById(id);
    const parents = f.getParents();
    const folder = parents.hasNext() ? parents.next().getName() : '(no parent folder)';
    // getSharingAccess: PRIVATE / DOMAIN / ANYONE_WITH_LINK, etc.
    console.log([
      f.getName(),
      f.getSharingAccess(),
      f.getSharingPermission(),
      f.getEditors().length + ' editors',
      'folder: ' + folder
    ].join(' | '));
  });
}

The first run asks for Drive authorization. Read the scope and keep the script pointed at your own documents.

To read the output, pick out any row that isn't PRIVATE, and any row whose folder is shared, then reopen those files' Share dialogs. I'd keep the script as a doorway to that check, not a replacement for looking.

If the screen doesn't match what you expect

• The sharing options differ from what you expected. On work or school accounts, an admin may restrict external sharing or "Anyone with the link". A missing option is more likely a policy than a bug. When you ask your admin, one sentence is enough: which sharing scopes does our organization allow?
• A Sheets export didn't happen. Tables with images can't be exported. Ask Gemini to return the table alone and try again.
• A Gmail export didn't arrive. It only creates a draft. Nothing reaches the recipient until you send it.

In every case, I check my own screen first. Where the help page is silent, I let the Share dialog and the folder answer, instead of filling in the blank with a guess.

One thing to do next

The next time you export an answer to Docs, open "General access" before you share anything. One place is enough for the first time; add the other two on the next export.

I keep this check even on the days I'm in a hurry.