[{"data":1,"prerenderedAt":177},["ShallowReactive",2],{"ls-connection":3,"support-article-pages-print-badges":5},{"connected":4},false,{"article":6,"related":39,"neighbors":109,"alternates":171},{"feature":7,"category":8,"locale":9,"slug":7,"title":10,"lede":11,"purpose":12,"steps":15,"notes":27,"generatedFrom":37,"updated":38},"print-badges","pages","en","Print attendee badges","Print one branded badge per registrant, with their ticket’s QR code, straight from the page.",[13,14],"For an in-person event, the badges are laid out for you: one card per registrant, in your brand, from the same list you work from at the door. Nothing to export and no file to build, the browser’s print dialog is the export, so a PDF comes free.","Each badge carries its holder’s ticket as a QR code, so at the door you scan the badge they are wearing.",[16,19,22,25],{"text":17,"image":18},"On the “Registrants” tab of an in-person page, click “Print badges”. It always prints the whole list, whatever search or arrival filter the tab is showing.","\u002Fsupport\u002Fprint-badges\u002Fen\u002Fstep-1.webp",{"text":20,"image":21},"The print view stacks one badge per registrant, alphabetically: your logo and accent color, their name, their job title and company when you collect them, their ticket’s QR code under the name, and the event with its venue.","\u002Fsupport\u002Fprint-badges\u002Fen\u002Fstep-2.webp",{"text":23,"image":24},"Pick the size (A7 or A6) and the layout (several badges per A4 sheet with cut guides, or 1 per page for a badge printer) then drop what you don’t want with the Logo, Job title, Company, QR code and Event date toggles. They are all on each time you open the view.","\u002Fsupport\u002Fprint-badges\u002Fen\u002Fstep-3.webp",{"text":26},"Click “Print”. Print at 100% scale, margins set to None and background graphics on, then cut along the dashed guides.",[28,29,30,31,32,33,34,35,36],"Badges print one per person, not one per booking: someone attending several days gets a single badge, and the date line only appears for someone attending one day.","Only what you collect can be printed: no job title in your form, no job title on the badge. With no name field, the badge falls back to the email.","The QR code is the person’s ticket: the scanner on the Registrants tab, the team link and the public link read the badge exactly as they read the ticket, with the same answers. See “Scan tickets at the door”.","The code holds the ticket alone, with no name, no email and no link, so a phone camera that is not your door scanner opens nothing. It prints black on white whatever your accent color: 24 mm on an A7, 34 mm on an A6.","Someone attending several days wears the same badge every day: the first scan checks them in for the whole event, and later scans answer “Already checked in” without turning them away.","A registrant anonymized by your data retention setting has no ticket, so their badge prints without a code, and the view says how many badges have none.","Moving someone to other dates keeps their badge valid. Deleting or anonymizing them stops it working at the door, like their ticket.","Someone you add at the desk (“Add a registrant”, or “On site” in the scanner) can be printed on their own right away: “Print badge” in the ⋯ menu at the end of their row. Their badge carries their code too.","Past 1000 registrants the stack is capped, and the view says so rather than quietly printing a partial list.","print\u002Fbadges\u002F[id].vue · print\u002FBadgeCard.vue · utils\u002Fbadges.ts (badgeQrSvg) · pages\u002F[id]\u002Fregistrants.vue (Print badges) · i18n badges.*","October 5, 2026",[40,62,88],{"feature":41,"category":8,"locale":9,"slug":42,"title":43,"lede":44,"purpose":45,"steps":47,"notes":55,"updated":61},"page-create","create-from-an-event","Create a page from an event","Start from a Livestorm, Zoom or Microsoft Teams event: its details pre-fill the page.",[46],"A registration page is always backed by an event. By starting from the event, the title, date, session and form fields are imported automatically. You copy nothing by hand, and the page stays in sync with the source.",[48,51],{"text":49,"image":50},"From the Pages tab, click “New page” to get started.","\u002Fsupport\u002Fpage-create\u002Fen\u002Fstep-1.webp",{"text":52,"image":53,"caption":54},"On step 1 · Event, choose the source (Livestorm, Zoom or Microsoft Teams once connected) then the event to promote. Search for it by name, or narrow the list: for Livestorm with “Status”, “From date” \u002F “To date” and “Event owner” (“Owned by me” keeps yours); for Zoom with “Event type” (Webinars or Meetings); for Teams with “Hosted by me”.","\u002Fsupport\u002Fpage-create\u002Fen\u002Fstep-2.webp","A source that is not connected yet offers “Connect” on its card.",[56,57,58,59,60],"The page comes pre-filled with the event's data: you move straight on to the form, then the design.","You need a connected account to see your events. See “Connect your Livestorm account”, “Connect Zoom” and “Connect Microsoft Teams”.","The Livestorm event does not exist yet? Create it from this same step. See “Create a Livestorm event from the builder”.","A single event can back several pages (per language, per campaign).","No connector, because the event happens in a room? Pick the “In-person event” card instead. See “Create a page for an in-person event”.","September 23, 2026",{"feature":63,"category":8,"locale":9,"slug":64,"title":65,"lede":66,"purpose":67,"steps":69,"notes":82,"generatedFrom":87,"updated":61},"livestorm-event-create","create-a-livestorm-event","Create a Livestorm event from the builder","The event your page promotes does not exist yet? Describe it on the Event step and it is created in Livestorm for you.",[68],"A page is always backed by an event. When that event is not in Livestorm yet, you do not have to switch to Livestorm, create it and come back to pick it: the builder’s Event step creates it for you, sessions included, and links the page to it.",[70,73,76,78,80],{"text":71,"image":72},"On step 1 · Event, pick Livestorm as the source, then click “Create a Livestorm event”, above the list of your events. The same button is offered when the list comes back empty.","\u002Fsupport\u002Flivestorm-event-create\u002Fen\u002Fstep-1.webp",{"text":74,"image":75},"The form takes the place of the list. Under “Event details”, fill the “Event name”, a “Description” and the “Event owner” (you by default, or another member of your Livestorm team). The “Slug”, the event’s address in Livestorm, follows the name until you edit it.","\u002Fsupport\u002Flivestorm-event-create\u002Fen\u002Fstep-2.webp",{"text":77},"Under “Sessions”, set the “Time zone”, then “Add a session” for each date: a date, a start time and an optional name.",{"text":79},"Adjust the “Room settings” if you need to: chat, questions, polls, whether everyone can speak, automatic recording and the replay for registrants. “Copy the settings of an existing event” takes them from one of your events instead, along with its registration form and emails.",{"text":81},"Click “Create event and continue”. The event is published in your Livestorm workspace, the page is linked to it and its details are pulled in like any picked event. A tag on the event card marks it as created from the builder.",[83,84,85,86],"Livestorm only: Zoom, Microsoft Teams and in-person events have no create button here.","Registration stays on the page you are building, so the new event’s own Livestorm registration pages are switched off.","Registration fields, emails and the room design use your Livestorm defaults. Adjust them in the event settings in Livestorm, then re-pull the event on this step so the page follows.","If Livestorm refuses a session or a session name, the confirmation under the event card lists each one with Livestorm’s answer. Add or rename it in the event settings before you share the event.","EventPicker.vue · event\u002FLivestormEventForm.vue · event\u002FCreatedEventBanner.vue · i18n wizard.event.create.*",{"feature":89,"category":8,"locale":9,"slug":90,"title":91,"lede":92,"purpose":93,"steps":95,"notes":104,"updated":108},"publish-page","publish","Publish your page","Take the page live at its public, crawlable and indexable address.",[94],"Publishing makes the page reachable at its public URL and opens it to registrations. It is also what makes it indexable by search engines, the whole point of a registration page.",[96,98,100,102],{"text":97},"On step 5 · Launch, check the preview of what visitors will get, and the search-engine visibility set on the Settings step.",{"text":99},"The preview is a short window on the top of the page. “Expand preview” (or clicking the window itself) reopens it full size and scrollable, so you can read the whole page before committing to it.",{"text":101},"Click “Publish page”, in the bar at the bottom of the step alongside the link that opens the page for real. Anything still blocking the publish is spelled out right there.",{"text":103},"The page always carries three tabs, “Overview” (its public address, the embed code and the numbers), “Registrants” (who signed up) and “Setup” (the builder you just used). Publishing is what unlocks the first two; before that they read “Available once the page is published”.",[105,106,107],"You can “Unpublish” at any time to take the page back offline: its public link then answers “page not found”, and you can publish it again whenever you like.","The link to share, and the code to embed the page on your own site, are both on the Overview tab.","Re-publishing after a change updates the public page in place.","August 3, 2026",{"prev":110,"next":147},{"feature":111,"category":8,"locale":9,"slug":111,"title":112,"lede":113,"purpose":114,"steps":117,"notes":132,"generatedFrom":145,"updated":146},"self-check-in-kiosk","Set up a self check-in kiosk","Put a tablet at the entrance where attendees check themselves in with their ticket, their badge or their email.",[115,116],"A self check-in kiosk is a tablet at the entrance of an in-person event. Attendees hold their QR ticket or badge up to its camera, or type the email they registered with, and the kiosk welcomes them by their first name. Your welcome desk is left with the guests who need help.","The kiosk wears your page’s brand, cover photo and fonts, and speaks the event’s language. A guest only ever sees their own first name: the kiosk never shows an email, the guest list or how many people have arrived.",[118,120,122,124,126,128,130],{"text":119},"Open the “Registrants” tab of an in-person page and click “Door check-in”. The kiosk is the last section of the dialog, “Self check-in kiosk”.",{"text":121},"Click “Turn on the kiosk”, read the three points it lists, then click “Turn it on”. The section now holds the kiosk’s link with a “Copy” button and, on a computer, a QR code of that link.",{"text":123},"On the tablet, scan the QR code with the camera app, or open the link you copied. The kiosk opens on a setup screen in the event’s language.",{"text":125},"Pick the camera. The front one, facing guests, is the default; switch to the back one if the tablet faces away from them. Then tap “Start kiosk”: the tablet goes full screen, the screen stays on and the camera opens.",{"text":127},"Lock the tablet on the kiosk so nobody can leave it: Guided Access on an iPad (Settings > Accessibility, then triple-click the side or Home button), App pinning on Android (Settings > Security, then pin the browser from the app overview).",{"text":129},"Guests hold their ticket or badge inside the frame, or type their email and tap “Check me in”. The kiosk answers “Welcome, Amara!” and is ready for the next guest five seconds later, or as soon as they tap “Done”.",{"text":131},"When the kiosk can’t find a code or an email, it says “We couldn’t find this ticket” or “We couldn’t find this email” and sends the guest to the welcome desk. After a code that isn’t a ticket, “Type my email” lets them try their email instead.",[133,134,135,136,137,138,139,140,141,142,143,144],"Guests get the same welcome whether or not they had already arrived. Checking in twice keeps the first arrival time, and someone booked on several dates checks in once for the whole event, as at the door.","The email has to be the one they registered with; capital letters don’t matter. Someone waiting for your approval or on the waiting list isn’t registered yet, so the kiosk sends them to the welcome desk.","The kiosk doesn’t register walk-ins. Your team adds them from the scanner’s “On site” tab or with “Add a registrant”: see “Scan tickets at the door”.","The email field empties after each try and after 30 seconds without a touch, so the next guest never sees an address. Nothing is kept on the tablet.","If your retention setting anonymizes registrants, they still check in with their email, and the kiosk welcomes them without a name.","Anyone with the link can open the kiosk, and it can only check in the guest standing in front of it. Keep the link to your tablets.","“Replace link” issues a new link and “Turn off” ends it. Either way, every tablet on the old link closes within a minute. Both are recorded in the audit log.","The kiosk closes by itself the day after the last date. It also closes if you unpublish or archive the page, or if the event is no longer in person.","When the tablet loses its connection, the kiosk says check-in is paused and sends guests to the welcome desk. Nothing is saved to send later.","A browser signed in to your account can’t start the kiosk: it asks you to sign out first, so no guest can reach your workspace from the tablet.","On an iPhone, web pages can’t go full screen, so Guided Access is what keeps the kiosk on screen.","Its look comes from the page, and it has no settings of its own: change the page’s brand or cover photo and the kiosk follows within a minute.","KioskLinkSection.vue · ScanLinksDialog.vue · scan\u002F[token].vue · KioskRoute.vue · KioskApp.vue · KioskView.vue · i18n scanLinks.kiosk* \u002F kiosk.*","October 8, 2026",{"feature":148,"category":8,"locale":9,"slug":149,"title":150,"lede":151,"purpose":152,"steps":154,"notes":163,"generatedFrom":170,"updated":38},"registrant-edit","correct-or-delete-a-registrant","Correct or delete a registrant","Fix a typo in someone’s answers, move which dates they hold, or erase them entirely.",[153],"A welcome desk spends its day on three things: printing a badge, fixing a name someone mistyped, and moving a person to another date. The ⋯ menu at the end of each row on an in-person page's Registrants tab holds the last two, plus the deletion you owe anyone who asks to be erased.",[155,157,159,161],{"text":156},"Open the “Registrants” tab of an in-person page, find the person, and open the ⋯ menu at the end of their row.",{"text":158},"“Edit info” opens their answers, each in the control it was collected with. Correct what is wrong, then “Save changes”.",{"text":160},"In the same dialog, “Sessions they attend” moves them between dates: tick the ones they hold now. At least one is required.",{"text":162},"“Delete registrant” erases them: every date they booked and every answer they gave. The confirmation names them, and it cannot be undone.",[164,165,166,167,168,169],"The email can't be changed: on a page the address IS the person. It folds their dates into one line, carries their arrival and signs their ticket.","The Livestorm terms consent isn't editable either: it records what the visitor themselves agreed to. Your own consent questions stay editable like any other answer.","Saving re-checks the answers you changed against the same rules the public form applies, so a required answer can't be emptied and a dropdown only takes one of its own options. An answer you leave alone stays as it was given, even one the form no longer offers.","Moving someone's dates keeps their registration date, their QR ticket and their arrival stamp. Answers to fields you have since removed from the form are kept too.","Deleting is the erasure you owe under GDPR: it also cancels any abandoned payment of theirs. Both editing and deleting are recorded in Settings → Audit.","A registrant anonymized by your data-retention policy has no answers left to correct, so the menu offers no edit for them. See “Set how long registrant data is kept”.","RegistrantEditDialog.vue · pages\u002F[id]\u002Fregistrants.vue (row menu) · i18n registrants.menu.* \u002F registrants.edit.*",[172,175],{"hreflang":173,"path":174},"fr","\u002Fsupport\u002Fpages\u002Fimprimer-les-badges",{"hreflang":9,"path":176},"\u002Fsupport\u002Fpages\u002Fprint-badges",1792141117372]