Back to the site한국어

ConferenceQ User Manual

Live multilingual conference Q&A — from setup to wrap-up

Screens use demo data. Join codes and names are examples.

Chapter 0

Before you start

ConferenceQ is one continuous flow: the audience joins by QR and asks in their own language, the question is translated and reviewed, and it reaches the presenter’s screen. This chapter lays out that flow and the people in it.

The four roles

RoleWhoWhat they do
AudienceAnyone who scanned the QRAsks and upvotes. Never signs in.
ModeratorDecides what goes outReviews, approves, hides, fixes translations, builds the running order.
Event ManagerThe team preparing the eventHandles events, sessions, QR codes, materials and the Glossary.
PresenterThe speaker on stageSees approved questions with original and translation together.

The path a question takes

  1. 1SubmittedThe audience writes in their own language
  2. 2TranslatedTranslated with the Glossary applied
  3. 3ReviewedA moderator approves or hides it
  4. 4QueuedIt joins the running order
  5. 5AnsweredThe presenter answers and marks it done

A role is a permission set, not a person. The same person can moderate one event and manage another.

Chapter 1

Signing up and signing in

You sign up as an institution, not as an individual. Whoever signs up becomes its first admin, and adds colleagues from the console afterwards.

Creating your institution

The institution and its first admin account are created together on one screen. If either half fails, both are rolled back.
  1. Institution name — shown as-is on the audience screen and in the console header.
  2. Institution subdomain — the address your attendees and staff arrive at. Lowercase letters, numbers and hyphens, 3–32 characters. Availability is checked as you type.
  3. Default time zone — the default for new events. Each event can override it.
  4. Admin account — name, email, password. Each requirement ticks off as you satisfy it.

The subdomain can’t be changed later. Every QR code and printed programme you hand out points at it. Pick a short name for the institution, not for one event.

Signing in

The admin sign-in screen. The language toggle is here too.

If you forget your password, an organization admin creates a reset link from User management and sends it to you. Open it, choose a new password, and you are signed in. The link expires after 24 hours and works once.

When sign-up completes you land on your institution’s own sign-in page (for example iso.conferenceq.live/admin/login). The certificate is issued automatically on that first visit — there is nothing to register. You can copy the address any time from Organization settings in the console.

Chapter 2

Preparing an event

Create the event, add its sessions, then prepare the QR codes, materials and terminology. This is everything you do before the day itself.

Create the event

The console’s first screen. Every event gets a join code automatically.

The join code is what your audience types at /join. An event code sends them to whichever session is running at that moment, so one printed code covers an event with many sessions.

Sessions and their status

Each session carries its status controls and links to the Moderation Queue, materials, audience view and Presenter View.
Session statusMeaning
SCHEDULEDScheduled. Not taking questions yet.
LIVERunning. Questions are open.
PAUSEDPaused. Submission closes; the screen stays.
ENDEDEnded. Questions and answers remain readable.
ARCHIVEDArchived. The Q&A page goes down and the materials are deleted.

Questions open only while the session is LIVE. While SCHEDULED, PAUSED or ENDED the audience can’t submit new questions, though existing ones stay visible.

Generating and handing out QR codes

All three QR types are generated for you. The panel on the right explains what each is for, plus printing tips.
TypeWhere it goesMeaning
Conference QREvent entryThe join screen arrives with the event code filled in. Use it on banners, signage and printed programmes.
Session QRDirect session entryScanning opens that session’s question screen straight away. Post it at the room door and on seats.
Presenter QRPresenter screenThis one carries an access token. Hand it to the speaker privately.

The Presenter QR carries an access token. Anyone with that link can open the presenter screen — hand it to the speaker privately and never put it on a banner, a seat or a printed programme.

Uploading presentation materials

PDF only. What you upload appears at the top of the audience session screen with a thumbnail.

Files are deleted when you archive the session. Ending it does not delete them — people still read the questions and answers of a finished session, and they need the deck alongside.

Glossary — pinning your terminology

Pin your domain terms so translations don’t drift. This is where ConferenceQ parts ways with a generic Q&A tool.

Priority runs Session > Event > Organization. When the same source term exists in several scopes, the narrowest one wins. A new term applies from the next translation onward — questions already translated are left as they are.

Branding

The preview on the right updates as you type. Only the logo image waits until you save.

Chapter 3

What the audience sees

The audience installs nothing and signs in to nothing. Scanning a QR or typing a code is the whole of it — but one of the two is required. The code is the key to the room.

A join code is required. There is deliberately no list of running sessions here — with one, anyone could post into any session without knowing its code.
Session details, materials, counts and the question list on one screen. The button at the bottom asks a question.
There is no language picker — the language is detected from what you type. Leave the name blank to stay anonymous.
Each card shows the original on top and the translation beneath. Tap the number on the left to upvote.

Taking part in a poll

When the moderator opens a poll, a card appears above the question list. Tap an option to see the results at once; you can change it until the poll closes.
The results stay for a while after the poll closes. The question list is still right below.

The clock at the top right is the time left. It turns red at ten seconds and the server closes the poll at zero. The server decides, not the clock on your screen — a tap at the very last moment may not be counted.

The join code is the door. Only people you handed a QR or a printed code get in. Code entry is capped at 10 attempts a minute so codes can’t be guessed. When the event is over, end the session to close new questions.

The original is never overwritten by its translation. Even when a moderator edits the translation, the original and the machine version both remain. Names are not translated either — they are what the person wrote.

The globe button at the top right switches between Korean and English. What changes is the interface wording; question text always shows the original and its translation together.

Chapter 4

The moderator’s working screen

During the event a moderator watches this one screen. Incoming questions on the left, the running order for the presenter on the right.

The five counters across the top tell you where things stand. A growing Pending number means the review backlog is building.
  1. Approve — the question appears in the audience list and in the Presenter Queue.
  2. Hide — it drops off the audience screen. This conceals rather than deletes; the record stays.
  3. Edit translation — fix an awkward rendering. Your edit is stored separately; the machine translation is kept.
  4. Re-check duplicates — rescan just that question for near-matches.

Two moderators can safely touch the same question. The first action wins and the second one is shown the current state instead. Nobody silently overwrites anybody.

Merging duplicate questions

Move the similarity threshold to find groups worth merging. The most-voted question is picked as the representative.

The groups here are only a suggestion. Nothing is merged until you press the button, and merging never erases the original text, its translation, or the votes.

On a narrow screen such as a tablet the right-hand panel is tucked away. The “Queue · Polls” button at the bottom right slides the Presenter Queue and polls out as a drawer.

Running a live poll

Polls sit at the top of the right-hand panel. An open poll’s bars move as votes arrive, with the time left beside them.
  1. New poll — one question and 2–8 options. Pick a time limit from 30 seconds to 10 minutes, or leave it to close by hand.
  2. Create and start — it appears on the audience, presenter and projector screens at that moment. Save only keeps it as a draft to start later.
  3. Close — you can close it early by hand. When the time runs out the server closes it for you.
  4. Reopen — open a closed poll again with a fresh time limit. Votes already cast are kept.

Each person gets one vote and can change it until the poll closes. There is no sign-in, so a vote is counted per browser — the same as upvotes. Results live on screen and in the Audit Log, not in the CSV export.

Running the Presenter Queue

The right-hand panel is the order the presenter will see: answering → queued → most voted. “Show on screen” makes a question the current one on the presenter’s screen; “Mark answered” takes it out of the queue.

Chapter 5

The presenter’s screens

The presenter has two screens: one they operate on stage, and one you put on the projector.

Presenter View — operated on stage

Big type on an ink background — a laptop on the lectern. Text size and the original/translation view can be changed on the spot.

Stage Display — for the projector or LED wall

No controls at all. The join code stays on screen so latecomers can still get in.

While a poll is open, the presenter screen shows the results above the question (the presenter can hide them), and the projector shows the results in place of the question. The projector’s join card now carries a QR code, so latecomers can join from the screen alone.

Both screens share one live session. When the moderator presses “Show on screen”, both update without a refresh.

Chapter 6

During and after the event

Keep the dashboard up while the event runs; afterwards, build your report from the analytics and the log.

Dashboard — what you watch during the event

The whole event at a glance. It refreshes every 30 seconds, so you can just leave it up.

Alerts watches for translation failures and a growing review backlog. Past 20 questions awaiting review it warns you — that is the moment to put a second moderator on it.

Analytics and CSV

Use this to build the report after the event. Set a date range to count only part of it.

Audit Log

A time-ordered record of who did what and when. It can’t be edited or deleted.

Users and the organization

Adding a user creates an invite link. Hand it to them; they open it, set a password and are signed in (valid for 72 hours). The last organization admin can’t be re-roled or deactivated.
Organization defaults and usage. Copy your institution’s address (subdomain) here. The identifier (slug) can’t be changed after creation.

Appendix

Question status reference

Status Meaning
SUBMITTEDReceived. Translation starts shortly.
TRANSLATINGBeing translated.
PENDING_REVIEWWaiting for a moderator. Not yet visible to the audience.
APPROVEDApproved and visible in the audience list.
QUEUEDSitting in the presenter’s queue.
ANSWERINGBeing answered right now.
ANSWEREDAnswered.
HIDDENHidden by a moderator. Not deleted.
DUPLICATEMerged into another question.
TRANSLATION_FAILEDTranslation failed. The original text is preserved.

Permission matrix

Organization AdminEvent ManagerModeratorPresenter
Organization settings···
User management···
Create events and sessions··
Manage the Glossary··
Analytics and Audit Log··
Approve and hide questions·
Edit translations·
Create and close polls·
Show a question on screen
Presenter View

Troubleshooting

Symptom What to check
The audience says they can’t submit a questionCheck that the session is LIVE. Submission is closed while SCHEDULED, PAUSED or ENDED.
Nothing is being translatedSaving a question is independent of translating it, so the question survives a translation failure. Failed ones collect under Translation Failed in the Moderation Queue, and the dashboard Alerts flags them.
Terminology keeps changing between translationsRegister the term in the Glossary. Terms apply from the next translation onward, so add them before the event.
Scanning the QR lands somewhere unexpectedA QR encodes the domain it was generated on. Before printing, check the URL under the QR is your real service address.
The presentation materials are goneArchiving a session deletes its materials too. That can’t be undone — keep your own copy before you archive.

ConferenceQ · conferenceq.live · mudotmusic@gmail.com