The Gemini share button fails and the error tells you nothing. Usually it isn't a bug and it isn't your file — public link sharing is off by default on work and school accounts, and the switch is one only an admin can flip. Here's how to tell, and what to do when you can't wait for them.
You built something in Gemini Canvas. A one-pager, a small app, a report for a client. You hit share, and Gemini tells you it could not create a public link.
The message says nothing about why. So you try again, then in another browser, then you rebuild the Canvas from scratch assuming something got corrupted. None of that helps, because in most reported cases nothing is broken.
In March 2026 Google announced that Workspace users could create shareable public links to their Gemini conversations — a capability that until then belonged to personal Google accounts only. The announcement carries the part that explains your error:
Public Gemini chat link sharing will be OFF by default and can be enabled at the domain, organizational unit (OU), or group level using a new control in the Admin console.
Read that against what you just did. You asked Gemini to create a public link. Your organization has not enabled public link creation. Gemini declined, and reported it as a failure rather than as a policy — which is why it reads like something went wrong on your end.
Google's Gemini Apps help page describes the same setting from the other side, for the case where the button doesn't appear at all: if you can't find the Share option, your organization may have disabled conversation sharing, and your Workspace administrator can turn it on or off. A missing Share and a failing Share are two faces of one switch.
One test settles it in under a minute.
Sign in with a personal @gmail.com account, build a throwaway Canvas, and share it. If the link generates there and fails on your work account, the variable is the account, and the only thing that differs between those two accounts is the organization policy. Not the file. Not the browser. Not the conversation.
If it fails on both, then you're looking at something else — an outage, a signed-out session, or one of the content restrictions Google documents for chats built with Gems and for accounts belonging to under-18 users. That's a genuinely different problem and worth reporting.
Worth naming the thing that wastes the most time here: rebuilding the Canvas. It is the natural instinct, it costs an hour, and it cannot possibly help — the policy applies to your account, not to any particular conversation. A brand-new Canvas hits exactly the same wall.
If you need public links on, the request goes to whoever runs your Google Workspace. Ask for it by name — public Gemini chat link sharing, in the Admin console — because that's specific enough for an admin to find and act on without a round of guessing.
It's a reasonable ask, and it's worth understanding why the answer is sometimes no. A public Gemini link publishes a conversation to the open web, and Gemini conversations tend to accumulate whatever context you pasted in — internal numbers, client names, a draft nobody has approved. Defaulting that to off is the right call for most organizations. The friction you hit is the side effect of a correct default, not somebody's oversight.
Which means: sometimes the honest answer is that the setting is going to stay off, and you still need to send the page today.
Public links aren't the only sharing switch. Google's Workspace admin help for Gemini conversation sharing lists two, with opposite defaults: sharing by public link is turned off by default, and sharing through Drive is turned on by default. It covers chats, Canvases, and generated media.
So when the public link fails, the Drive route may well be open. Three things to know about it, per the same page:
For a colleague, or a client your organization's Drive lets you share with, that may be all you need. For a client who shouldn't need a Google sign-in, it isn't — which is where the next section comes in. (Google's page was last updated 10 September 2026; we checked it on 15 September.)
The route around a blocked publish is to stop trying to publish the conversation and take out the thing you actually made.
Ask Gemini, in the chat, for the complete HTML of what it built — a single file, with the CSS and JavaScript inline. Copy what it gives you, paste it into a text editor, and save it with a .html extension. Double-click it. It opens in any browser, on any machine, with no account and no Gemini session involved.
This step exists because Canvas has no download-as-HTML button. Google's Canvas documentation lists export paths to Docs, Slides, and Colab for Python — useful, but none of them hand you the page itself. Asking for the code in the chat is the practical substitute, and it works.
Two things worth checking on the file before you send it, both of which come up constantly with AI-generated pages:
Once that file exists, the Workspace policy is no longer in the loop. You have a page, and where it goes next is your decision rather than your admin's.
If your admin does enable it, it's worth knowing what you're sending. Google's Canvas documentation states that anyone with the public link can view and edit data associated with the app, and a shared conversation can be continued by whoever opens it.
For a colleague you're collaborating with, that's the point. For a client deliverable it can be surprising — closer to handing over a working copy than to sending a finished page. It's also a public link, so it isn't restricted to the person you sent it to and isn't tied to their identity; anyone who ends up with the URL has the same access. Which AI shares are public, and what unsharing actually undoes walks through the same distinction on Claude's side, where the mechanics are close cousins.
Once you're holding a .html file, hosting it is a separate question with a lot of good answers. If the page is meant to be found — a portfolio, something you want indexed — a public host is the right shape, and the free options are genuinely good: GitHub Pages, Netlify Drop, Cloudflare Pages.
If the page is a deliverable for specific people, that's the job miinideck is built around: drop the file, get a link that search engines don't index, add a password if it needs one, and update the same link when the page changes. It's what we optimise for.
And the honest boundary: if what Gemini built for you needs a database, a login, or a server that runs code, none of this applies — that's not a file you can hand over, and Vercel or Netlify are the right tools for it. Canvas apps are usually self-contained, but not always. Check before you assume.
The error isn't about your file. Public Gemini link sharing is off by default on work and school accounts, the switch sits in the Admin console, and no amount of retrying moves it. Either ask your admin to turn it on, or ask Gemini for the HTML and take the page with you.
The second option is the one that keeps working regardless of what anyone decides — which is a reasonable argument for getting a file out of the chat by habit, not just on the day something blocks you.
A disabled Publish button isn't one bug — it's four different situations wearing the same grey. Two of them are permanent, two clear in a minute. Here's how to tell which one you're looking at, and how to get the page to the person waiting for it either way.
The message is about Anthropic's side, not yours, and it usually clears on its own. The risk isn't the outage — it's what people press while waiting. Here's the safe order of operations, and how to get the work out of the artifact while you wait.
You built something in Claude, came back weeks later, and it's gone. Usually it isn't deleted — it's sitting inside a conversation you can no longer find. Here's how to get it back, and the one case where it really is unrecoverable.
miinideck turns a single HTML file into an unguessable link with optional password and expiry. Default-private, never indexed.