Step 1
Set up your event app
Answer these questions once, in any order. At the end you'll export one config file and a checklist of everything you said you'd provide. Give the file to Claude with the td-synnex-event-app skill, and Claude builds exactly what you chose, asking only for what's still missing. Your answers save in this browser as you go.
Never type secrets here. No API keys, PINs, passwords, event codes, card numbers, attendee emails or phone numbers, or sales figures. You'll type secrets at the terminal during setup, and attendee files are attached in the chat.
About 15–20 minutes. Anything you don't know yet can stay blank or be marked "Later". Look for the ? next to a question for a quick explanation, and the dashed boxes for a deeper look at how something works.
Step 4
Choose your features
Pick a preset, then add what you want. If an option needs something you haven't picked, it says what and why, with a one-click way to turn it on. What does each option do?
Preset
Team tools come with Live event. Staff from your host company sign in as themselves, then use the shared team PIN to post announcements (info or urgent) that appear as a banner on every phone, and to remove photos. Add PIN sign-in below if you also want each person's sign-in protected, with an admin panel for your team.
Security and access
Two separate locks. The event code decides who can open the app at all. PIN sign-in decides who can act as a given attendee once they're in. Use either, both or neither.
How sign-in, account claims and the admin panel work
Without PIN sign-in (Live event's default), an attendee taps their name in the list and that phone becomes them. It's quick, but it isn't a password: whoever taps a name first gets it.
With PIN sign-in, claiming a name works like this:
- First claim: the attendee taps their name and sets a 4-digit PIN. That phone is now signed in as them.
- Second device: a laptop or new phone asks for the same PIN. Notes and starred people follow the person, not the phone.
- Name already taken? The real person taps "That wasn't me". Your team gets a red badge in the app (and an optional email).
- Restoring a name: an admin checks the person's ID face to face, resets the claim, which signs out every device using that name, and reads out a one-time code (good for 24 hours). The attendee enters it and sets a new PIN.
- Guessing is stopped: 5 wrong PINs lock that phone for 15 minutes, and 10 wrong in a day pause new sign-ins for that person and alert your team.
The admin panel lives in Info, Team tools. Only staff from your host group can open it, and only with the admin PIN on a phone that's signed in as them. It shows open reports, every attendee's sign-in state and devices, and the reset, new code, undo and sign-out actions.
Under the covers: PINs and codes are stored only as salted HMAC-SHA256 hashes with a secret pepper that lives on the server, so a copy of the database can't be used to work them out. Every limit is enforced on the server, never in the page. Full explanation in the guide.
The page
If you don't know, choose Not sure; Claude will check the address.
A placeholder is fine for now. It must be final before you print QR codes.
Company CMSs and SharePoint usually strip scripts, so the app won't run there. Claude will suggest a static host your IT team can approve, or free GitHub Pages, and can draft the request.
The backend
Your choices need a small backend. The tested option is a free Cloudflare account; your page doesn't move.
Profile photo upload needs the free Cloudflare backend.
Only matters for very busy photo walls.
Some company proxies block the backend's address; test early.
Event code: keeping the source private
The code only protects the page if its unlocked source files aren't public. A public GitHub repo exposes them.
Locations
Add the venue, meeting rooms, meals, dinner spot, hotel and any activity. If attendees sleep at the venue, add it again with the role "Hotel".
Nothing to fill in here. The features you picked don't need staff groups, operators or approvers. Choose Next to carry on, or pick more features in step 4.
Who's who
The app keeps three kinds of people apart: your host company (the staff running the event), partners or sponsors, and attendees. Groups drive the directory filters, badge colors and who gets the team tools.
Live event
Announcements show as a banner at the top of every phone, as "info" or "urgent", and expire after the hours you set. Your team PIN holders (above) post them in the app; an operator can also post from the command line.
Live polls and Q&A
Polls and questions open 15 minutes before a session and close 30 minutes after it. Votes and questions are anonymous unless someone signed in chooses to show their name.
Your team PIN holders run the polls. Presenters can't, because they aren't on a list they can sign in from.
Profile photos
Adding a photo is always optional. People crop it on their phone, location data is stripped, and they can remove it any time. Your staff can remove any profile photo, and every uploaded photo is deleted on your sign-in data deletion date.
Security and sign-in
Who holds which key. The code and PINs themselves are chosen at the terminal during setup, never typed here.
Approvers
A named person signs off on each of these before anything appears.
Documents and Claude models
Tell Claude what you'll attach in the chat. Mark anything not ready as "Later", and paste it in when it arrives, especially the know-before-you-go email.
Anything else
Your checklist
Everything you said you'd provide, in one place. Tick things off as you gather them; the ticks save in this browser.
Export
Download saves the file you give to Claude. Some viewers, such as a page shared from Claude, block downloads. If nothing happens, use Copy and paste the text into the chat.
See the config file
What to do next
Saving the config in a folder that's a public repo? It holds no secrets, but it does hold staff names and your event plan. Keep it out of public repos if that matters.
Start over