[{"data":1,"prerenderedAt":165},["ShallowReactive",2],{"support-article-pages-print-badges":3,"ls-connection":163},{"article":4,"related":31,"neighbors":98,"alternates":157},{"feature":5,"category":6,"locale":7,"slug":5,"title":8,"lede":9,"purpose":10,"steps":12,"notes":24,"generatedFrom":29,"updated":30},"print-badges","pages","en","Print attendee badges","Print one branded badge per registrant, straight from the page.",[11],"For an in-person event, Venue lays the badges 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.",[13,16,19,22],{"text":14,"image":15},"On the “Registrants” tab of an in-person page, click “Print badges”. The button carries the date filter showing at the time, so a one-day door prints that day only.","\u002Fsupport\u002Fprint-badges\u002Fen\u002Fstep-1.webp",{"text":17,"image":18},"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, and the event with its venue.","\u002Fsupport\u002Fprint-badges\u002Fen\u002Fstep-2.webp",{"text":20,"image":21},"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 and Event date toggles.","\u002Fsupport\u002Fprint-badges\u002Fen\u002Fstep-3.webp",{"text":23},"Click “Print”. Print at 100% scale, margins set to None and background graphics on, then cut along the dashed guides.",[25,26,27,28],"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.","A walk-in who registers at the desk can be printed on their own, from the print button on their row.","Past 1000 registrants the stack is capped, and the view says so rather than quietly printing a partial list.","print\u002Fbadges\u002F[id].vue · pages\u002F[id]\u002Fregistrants.vue (Print badges) · i18n badges.*","July 31, 2026",[32,53,74],{"feature":33,"category":6,"locale":7,"slug":34,"title":35,"lede":36,"purpose":37,"steps":39,"notes":47,"updated":52},"page-create","create-from-an-event","Create a page from an event","Start from a Livestorm or Zoom event: Venue pulls its details to pre-fill the page.",[38],"A Venue 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.",[40,43],{"text":41,"image":42},"From the Pages tab, click “New page” to get started.","\u002Fsupport\u002Fpage-create\u002Fen\u002Fstep-1.webp",{"text":44,"image":45,"caption":46},"On step 1 · Event, choose the source (Livestorm or Zoom when connected) then the event to promote. Search for it or filter by “Hosted by me”.","\u002Fsupport\u002Fpage-create\u002Fen\u002Fstep-2.webp","Teams as a source shows “Not configured” until it is set up on your Venue deployment.",[48,49,50,51],"Venue pre-fills the page with the event's data: you move straight on to the form, then the design.","You need a connected Livestorm or Zoom account to see your events — see “Connect your Livestorm account” and “Connect Zoom”.","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”.","July 30, 2026",{"feature":54,"category":6,"locale":7,"slug":55,"title":56,"lede":57,"purpose":58,"steps":60,"notes":69,"updated":73},"publish-page","publish","Publish your page","Take the page live at its public, crawlable and indexable address.",[59],"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 Venue page.",[61,63,65,67],{"text":62},"On step 5 · Launch, check the preview of what visitors will get, and the search-engine visibility set on the Settings step.",{"text":64},"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":66},"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":68},"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”.",[70,71,72],"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",{"feature":75,"category":6,"locale":7,"slug":75,"title":76,"lede":77,"purpose":78,"steps":80,"notes":93,"updated":73},"track-registrations","Track registrations live","See who signed up on the page, with the answers they gave.",[79],"A published page has a Registrants tab that lists everyone who signed up through it, with the answers they gave. It is the drill-down behind the registration counter on the Overview tab.",[81,83,85,87,89,91],{"text":82},"Open a published page and select the “Registrants” tab.",{"text":84},"Read the table: one row per person, with the email, the date they registered and their answers. The counter says how many are loaded; “Load more” fetches the next batch.",{"text":86},"Search by email or by any answer to find someone. The search runs over the registrants already loaded, so load more if you cannot find them.",{"text":88},"On an event with several dates, the “Sessions” column names every date each person signed up for — one line per person, whatever they booked.",{"text":90},"For a Livestorm or Zoom event, “Open in Livestorm” opens the event’s own full registrant list.",{"text":92},"The menu at the end of a row corrects or removes that person: “Edit info” reopens the answers they gave (their email identifies them, so it stays fixed), and “Delete registrant” removes them from every date they booked.",[94,95,96,97],"The tab unlocks at publication: nobody can have registered to a page that was never published.","Only the sign-ups made through this page appear here; the event keeps its own list on its platform.","The total, the views and the conversion rate live on the Overview tab, which also shows the latest sign-ups — see “Measure views and conversion”.","On an in-person page this table is also your door, and each row gets a ⋯ menu — see “Check registrants in at the door” and “Correct or delete a registrant”.",{"prev":99,"next":133},{"feature":100,"category":6,"locale":7,"slug":100,"title":101,"lede":102,"purpose":103,"steps":105,"notes":122,"generatedFrom":132,"updated":30},"scan-tickets","Scan tickets at the door","Check people in by scanning the QR ticket their registration issued — yourself, or with whoever works the door.",[104],"Every registration to an in-person event issues a QR ticket: the visitor gets it on the confirmation, at a link they can keep. At the door you scan that code instead of looking anybody up — on your own device, or on the phone of whoever is standing there, through a link.",[106,109,112,114,116,118],{"text":107,"image":108},"Open the “Registrants” tab of an in-person page and click “Door check-in”. Every row also carries a QR button beside its check-in control.","\u002Fsupport\u002Fscan-tickets\u002Fen\u002Fstep-1.webp",{"text":110,"image":111},"The dialog offers the three ways to work the door: scan on this device, a link for your team, or a link for anyone.","\u002Fsupport\u002Fscan-tickets\u002Fen\u002Fstep-2.webp",{"text":113},"“Scan tickets” opens the camera on this device. Point it at the visitor’s code: each scan answers with a verdict — “Checked in”, “Already checked in” (with the time they arrived), or “Not a valid ticket for this event”. The scanner stays open, so a queue moves through one code after another.",{"text":115},"Handing the door to someone else? The team link opens the same scanner for anyone signed in to this workspace — copy it, or scan the QR beside it with the phone that will work the door.",{"text":117},"Door staff with no Venue account — a volunteer, the venue’s own team, an agency — need the public link, which is off until you create it. Read what it allows, create it, then share it with that team only.",{"text":119,"image":120,"caption":121},"Someone lost their ticket? Open it from their row and copy the link. The ticket page shows no personal details, so it is safe to send as is.","\u002Fsupport\u002Fscan-tickets\u002Fen\u002Fstep-3.webp","The organizer’s copy of a ticket, reopened from the registrant’s row.",[123,124,125,126,127,128,129,130,131],"A scan only ever stamps an arrival, it never removes one. Undoing stays on the row’s check-in control, in the dashboard.","A ticket identifies a person, not a date: someone booked on several dates is admitted with the same code every day.","Scanning the same ticket twice keeps the first arrival time and answers “Already checked in”.","The public link is a key, not a password: anyone who opens it can check people in without signing in, and each scan shows them the attendee just admitted. Share it with the door team only.","“Replace link” issues a new one and kills the old one at once — that is the move if a link reached the wrong people. “Turn off” ends it entirely. Both are recorded in the audit log.","A public link never exposes your registrant list: it can admit people and read the arrival counters, nothing else.","A ticket link carries no name and no email. Identity only appears to whoever scans it.","Erasing a registrant, or anonymizing them through your retention setting, stops their ticket link from resolving.","Tickets are issued on registrations to an in-person event: an online event has no door, so no ticket.","pages\u002F[id]\u002Fregistrants.vue (door button) · ScanLinksDialog.vue · t\u002F[token].vue · ticket-token.ts",{"feature":134,"category":6,"locale":7,"slug":135,"title":136,"lede":137,"purpose":138,"steps":140,"notes":149,"generatedFrom":156,"updated":73},"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.",[139],"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.",[141,143,145,147],{"text":142},"Open the “Registrants” tab of an in-person page, find the person, and open the ⋯ menu at the end of their row.",{"text":144},"“Edit info” opens their answers, each in the control it was collected with. Correct what is wrong, then “Save changes”.",{"text":146},"In the same dialog, “Sessions they attend” moves them between dates: tick the ones they hold now. At least one is required.",{"text":148},"“Delete registrant” erases them: every date they booked and every answer they gave. The confirmation names them, and it cannot be undone.",[150,151,152,153,154,155],"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 same rules the public form applies, so a required answer can't be emptied and a dropdown only takes one of its own options.","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.*",[158,161],{"hreflang":159,"path":160},"fr","\u002Fsupport\u002Fpages\u002Fimprimer-les-badges",{"hreflang":7,"path":162},"\u002Fsupport\u002Fpages\u002Fprint-badges",{"connected":164},false,1787923385348]