Embedding a session
A session can be embedded in another web page - an intranet article, a course page, an event site - so people answer without leaving it. The embedded view is the same participant client, without Murmle's header: an embedded participant gets every question type. Because the header is where the language and animation choices live, an embedded participant uses the language their browser asks for and their device's motion setting.
The markup
Use an iframe pointing at the session's join code:
<iframe
src="https://murmle.example.org/embed/123456"
title="Weekly team pulse"
width="100%"
height="640"
style="border:0;border-radius:12px"
allow="clipboard-write"
></iframe>
The join code is shown on the presenter's screen and beside each open run in the activity's Runs list in the console, which also has an Embed button with these attributes ready to copy. A join code belongs to a session only while it is open, so embed a session that is running or about to run.
Keep the title: an untitled frame cannot be identified by a screen reader. Adjust height to
suit your page.
Which sites may embed
Browsers will only show the frame on pages the Murmle deployment allows. The list of allowed
origins is set per deployment by its operator (POLLINATOR_EMBED_ANCESTORS, a
space-separated list of origins), and by default it is empty - no site may embed. There is no
per-workspace setting.
If the frame stays blank, the host page's origin is almost certainly not on the list. Nothing in Murmle's logs will say so, because the browser refuses the frame before any request is made; ask the operator to add the origin.
Everything other than the embed view - the console, the presenter view, sign-in and the launch pages - refuses to be framed by another site.
What an embedded participant is
An embedded participant joins the session like anyone else, under the session's privacy mode. They are not signed in through your site, so an embed is not a way to report outcomes against your own users - use a launch for that. Launches cannot run inside a frame, because browsers partition the storage a participant credential lives in.