Skip to content

Gemini sharing — the fine print

The highest-staleness details behind the Share a Gemini Gem or Canvas option page: when Gem sharing launched, how account type bounds reach, the Editor-can-delete risk, and where the docs go silent.

Last verified: 2026-06-08

Gem sharing is recent and rides on Drive

Gem sharing launched 2025-09-18 and is built on Google Drive's share machinery — shared Gems live in a Drive folder, so your org's Drive rules govern how far one travels. Switching a Gem back to Private removes it from a recipient's Drive. [confirmed]

Account type decides reach

Only personal Google accounts can share publicly or to anyone-with-the-link (a public Gem is even findable in Google Search). A work/school (Workspace) account is bounded by admin Drive policy: an admin can cap external sharing or turn Gem sharing off entirely, since "the sharing settings for Drive also apply to Gems." [confirmed]

Editor can delete your original

Editor isn't just "can change the text" — it can re-share, rewrite, or delete the Gem you built. For most hand-offs share as Viewer, or tell people to make their own copy. [confirmed]

Where the docs go silent

  • Whether an already-copied share link keeps working after you switch a Gem to Private. [unclear]
  • Whether opening a shared Canvas needs a Google account (the "no sign-in" guarantee is documented for Gems, not Canvas). [unclear]

The Drive/device-files-only catch

A Gem carrying knowledge files only shares if those files are Drive or device uploads — not a connected code folder or Gmail. Swap them to Drive uploads before sharing. [confirmed]

Sources