Publishing & sharing
Sharing a link and embedding
Public links, iframe embeds, and what each one exposes.
The share link
A published experience has a link of its own — the address the Share dialog copies. It always serves your latest published version.
It is not a public link. Whoever opens it has to be signed in, have confirmed their email address, and belong to your organisation. Somebody outside your organisation who is handed the link gets "not found" rather than a sign-in prompt.
That is the right behaviour for anything that records work, because an attempt has to belong to somebody. The token in the link is unguessable, but it is an address rather than a password — the gate is what keeps strangers out.
⚠️ So this is not the link to send to a class who have no accounts. Getting learners in is its own question, with three answers and no painless one: read Getting a class into your experience before you hand anything out.
If you need an address that works with no account at all, that is the embed, and it comes with a real trade: see Embedding an experience in a page.
Embedding
Embed gives you an iframe snippet for a web page, intranet or course tool.
⚠️ An embed is a different address from your share link, and nothing a learner does inside it is recorded — no activities, no attempts, no contributions. Do not embed a task you intend to mark. Read Embedding an experience in a page first.
An embed moves with every future publish. If one group has to stay on one version, give them that version's own link rather than freezing the experience for everybody — see Sending a class to one version.
Embeds need a reasonable amount of height. A 360° scene in a 300px-tall frame is unusable; give it at least 500px, more if the page allows.
Unpublishing
Unpublishing takes the experience out of circulation. Existing links and embeds stop resolving. Attempts already recorded are untouched.