Organizer accounts are created by the chamber. Participants don't sign in here — they use the Participant page and a claim code.
No events have been assigned to your account. Ask the platform team to add you to the event you are running — you will see it here the next time you sign in.
Paste or upload a spreadsheet saved as CSV. Only a Name column is required — everything else is optional, and the headers can be whatever your file already calls them. Each imported entry gets its own invite link automatically.
Read the code out to them and send them to /reset.html. It lasts an hour and works once. You can do this for participants in your own events; only the platform team can reset another organizer.
Every entry gets an invite link the moment you add it. Send a participant their link and they set a password once — no code to read out, nothing for you to type. The link stops working after they use it.
Post one link and one code wherever you already talk to participants — your newsletter, a Facebook group, the email you were going to send anyway. They open it, enter the code, find their own name in the list and set a password. Nothing to send individually.
The trade: anyone with the code could claim the wrong entry. For a town event that is unlikely, and you can see who claimed what below and take an entry back. Rotate the code if it gets out.
Sending from the address your
participants already know lands better than a brand-new domain would, and costs
nothing. Download CSV above gives you name, organization, email,
invite_link — the columns a mail merge wants.
«name» and «invite_link» where the message
below has them, then send.One code per stop, printed on the sign there. Players type it in to collect the stop. Edit any of them to a word of your own — filling in missing codes never changes one you have already handed out.
Sets the accent on every screen for this event. Each viewer still picks their own light, dark or seasonal background.