Help

Getting started

1. Choose a delivery mode and invite participants

Facilitator-driven workshops follow the activity the facilitator opens. In Self-directed workshops, each participant moves through the configured order independently. Their path is forward-only, and a waiting lobby is unavailable. Choose the mode before participants join.

Participants join using a workshop code, link, or QR code. The facilitator chooses the access mode. Some modes ask for a display name only; email sign-in modes send a one-time link. Understanding assessments use verified-email sign-in and show their own purpose, recipients, retention, rights, and intended-use information.

2. Pick the activity for the job

Ideation collects participant stickies. Categorise sorts ideas into facilitator-created buckets. Value/Effort places ideas on a two-axis grid. Vote allocates a participant budget to ideas or clusters. Wordcloud collects short words, and Statement collects short written responses. Survey gathers configured question responses. Likert gathers scored statements. Slide presents facilitator-authored content. Quiz supports either an entertainment leaderboard or a separately governed understanding assessment.

3. Build the activity hierarchy

Add an Introduction before an activity when participants need instructions first. A chained whiteboard needs a parent because it carries forward authored ideas from that parent. Any whiteboard type can parent any other whiteboard type, including repeated or longer chains; the dependency is about carrying ideas forward, not about a fixed type pairing. A child of a Categorise board is the one case where setup offers bucket/source selection when it opens. Slides are presentation-only and cannot be chain parents or children. An Introduction is a pre-activity presentation phase, not a standalone whiteboard dependency.

Use the Setup tab to add, reorder, archive, and configure activities. Open one activity at a time in facilitator-driven delivery. For a direct Categorise parent, select the source buckets when the child opens. Check the activity order and introduction text before sharing the join link.

4. Self-directed progression and activity restrictions

In a Self-directed workshop, participants acknowledge an Introduction before contributing to its activity, then move forward using Next or Skip where the activity allows it. They cannot return to an earlier activity. Once a participant progresses, the structure of Survey and Likert questions is fixed.

Entertainment Quiz activities cannot be included in Self-directed workshops. Only understanding-assessment Quiz activities are supported there; assessment participants use verified email. Review the assessment notice before inviting them.

5. Participant flow and operational basics

Participants join with the workshop code, link, or QR code and see only the activities opened for them. In facilitator-driven delivery, the facilitator opens and advances the room. In Self-directed delivery, each participant follows the configured order independently. Keep the join mode, lobby choice, and delivery mode aligned with the information being collected. Close joining when the intended group is present, and use the People tab to review the lobby and remove a participant if needed.

Before a live session, test the join link, open the first activity, and confirm the introduction and chain source. During a session, use the Run tab for the live board and the Results tab for the dashboard, exports, and a read-only share link. A share link is accessible to anyone who receives it; use it only for the result content you intend to disclose.

6. Reuse setup, templates, and supported formats

Personal templates save authored activity or workshop setup, not participant responses. Portable personal-template files are limited to 2 MiB. Uploaded images are omitted from portable templates, so upload them again after import. Quiz activities are excluded from personal templates and from workshop setup import and export at present.

Workshop setup JSON contains supported settings and authored activity setup, not participant data or responses. Importing it asks for confirmation and replaces the selected workshop's activities and setup while keeping that workshop's identity and name. Survey question imports support the formats shown in the facilitator console; review imported setup before inviting participants.

7. Results and privacy floors

Facilitators can export workshop results as JSON, CSV, or PDF. Cluster parents and every child sticky are retained in result output; clustered children carry the cluster name so their source is clear. JSON keeps the cluster nesting, while CSV and PDF keep clustered items together. Survey and Likert response detail follows their reveal and response-count rules. Unrevealed Vote tallies stay hidden from public result links, and small Likert groups stay below the configured privacy floor.

Result links, uploaded images, participant progress, responses, and templates are workshop data. Review Privacy and data and the deployment-specific privacy notice before collecting personal or sensitive information. Do not treat a display name, email sign-in, or a pseudonymous quiz handle as proof of identity.

8. Use integrations deliberately

Core scoring is deterministic and no live AI provider or model integration is active. Microsoft Planner is dormant unless deployment configuration enables it.