The same page, a different tool
AI tools now make finished work: a one-page proposal with a flow chart, a board report, a slide deck that runs in a browser. Claude calls them artifacts, ChatGPT has canvas, and Gemini has its own canvas too. Each tool lets you share what it makes, and each does it best with people who use the same tool.
Business documents rarely stay inside one tool. A proposal goes to a customer whose company standardised on Copilot. A contract goes to a lawyer who doesn't use AI at all. A board paper goes to directors who just want to read it and say what's wrong. The question is how they read it, mark it up, and get their comments back to you.
Sharing a Claude artifact
Claude's sharing is well thought through. You can share an artifact with your organisation, with anyone signed in to Claude who has the link, or with people you invite by email, and set whether each can view, comment or edit, depending on the kind of artifact.
The catch is in Anthropic's own help: everyone needs a Claude account, and people without one can't open a shared artifact, even with the link. The exception is an older-style artifact published from a chat, which anyone with the link can view and use. On Team and Enterprise plans, sharing outside your organisation is off until an owner turns it on. (From Anthropic's help on sharing artifacts, as it read in October 2026.)
That's a sensible design for people who use Claude. For a customer who doesn't, it means asking them to sign up for your AI tool before they can read your proposal.
Sharing a ChatGPT canvas
ChatGPT shares a canvas as a link. Anyone with the link can open it, and can take their own copy to work on in ChatGPT. That makes it easy to show someone something. It isn't built for review: its help doesn't describe seeing who opened it, comments from named people pinned to the text, or bringing several people's feedback back together. OpenAI changes these features often, so check its help for what canvas sharing does today.
Gemini, Copilot and the rest
Every major tool has some way to share, and each is shaped around its own users and its own workspace. Whatever the tool, the page itself is usually HTML, and it can be downloaded. That HTML is the part that travels. The trouble is what happens next: email often blocks or strips HTML attachments, because phishing uses them, and nothing in an inbox lets several people mark up a web page together.
Side by side
| Claude artifact sharing | ChatGPT canvas link | aihops | |
|---|---|---|---|
| Works with | Artifacts made in Claude | Canvases made in ChatGPT | Work from any AI tool, and PDF and Word |
| The people you share with need | A Claude account (except older artifacts published from a chat) | The link | An email address, and a free aihops sign-in with an email code or Google |
| Who can open it | Your organisation, anyone signed in to Claude with the link, or people you invite | Anyone with the link | Only the people you add |
| Comments | On some kinds of artifact, for people with comment access | Not described in its help | Comments, suggested edits, questions, issues and pricing notes, pinned to the words, from named people |
| See who has read it | Not described in its help | Not described in its help | Who opened it, and for how long |
| Everyone's feedback into the next version | By hand | By hand | AI consolidates it, every change explained, and you choose what goes in |
Claude and ChatGPT as their own help described them in October 2026. Both change quickly.
Sharing it through aihops
aihops is the neutral place in between. It takes the page from whichever tool made it and shares it with whoever needs to read it.
- Get the page in. From Claude or ChatGPT, connect aihops once and ask: "Share this on aihops with sam@customer.com." From anything else, download the HTML and upload it, paste it, or email it as an attachment to share@aihops.com.au. PDF and Word work too.
- Choose how to share it. Share it and each person gets their own copy, with comments only they see, and you see who opened it and for how long. Or collaborate, and everyone marks up one copy together.
- They read and mark it up. They get an email, sign in with a code sent to their address, and the page is waiting, working as it did when it was made, scripts and all, in a sandbox walled off from aihops.
- Make the next version. Ask AI to consolidate everyone's mark-up. Each proposed change shows what it replaces, why, and whose comments it answers. Keep what's right and publish, and everyone sees what changed.
Sharing and collaborating are free. AI reviews and consolidations come with 5 free uses, then Pro at A$20 a month. We don't use your content to train AI models, and we don't sell it.
When built-in sharing is the right call
If everyone involved uses the same AI tool, its own sharing is the shortest path, and Claude's in particular does a lot. If you just want to show someone a page and don't need anything back, a link is fine. aihops earns its place when the people you need are in another organisation or another tool, when you need their comments on the record, and when those comments have to become the next version.