How to run your first live session

Starting a session takes a snapshot of the template's steps. From that moment the session runs off its own copy: editing the template has no effect on the running room, which is what makes it safe to prepare next week's version while this week's is live.

You get a 6-character join code and a join link. Read the code out, put the link in the chat, or project it.

They enter the code and a display name. That is the whole flow — no account, no email, no install. The display name is what identifies them on your dashboard, so ask for whatever convention you need before you start.

If someone joins late, they land on the current step; earlier steps show as not started and they can work back through them if lookback is enabled.

Pacing is per-session configuration, not a property of the content. The same workshop runs self-paced with one group and tightly host-paced with the next.

• Lookahead — may participants move past your current step?
• Lookback — may they return to earlier steps?
• Force sync — pull everyone to the host's step as you advance
• Advance or jump the whole room to a specific step at any time

Each participant marks every step in progress, done or stuck. The dashboard shows the grid live and sorts stuck participants to the top. Raised hands and help requests form a separate queue with an explicit resolve action, so a question cannot scroll away.

Presence is derived from a heartbeat rather than stored, so a participant who closed their tab greys out as “Away” and frees their seat instead of inflating your count.

A broadcast reaches everyone at once as a banner or a modal. It can be a plain announcement, an acknowledge prompt (so you can see who has confirmed), or a single- or multiple-choice poll aggregated live.

Ending the session produces the report: a timeline, per-participant progress, engagement stats, broadcast results, quiz outcomes and the annotations people left. Export it as Markdown.

Free has sessions up to 45 minutes and Pro sessions of any length; where there is a limit the host sees a live countdown, and a session nobody is in ends on its own, so a forgotten one does not run indefinitely.