[{"data":1,"prerenderedAt":144},["ShallowReactive",2],{"support-article-settings-require-approval":3,"ls-connection":142},{"article":4,"related":32,"neighbors":112,"alternates":136},{"feature":5,"category":6,"locale":7,"slug":8,"title":9,"lede":10,"purpose":11,"steps":14,"notes":26,"generatedFrom":30,"updated":31},"registration-approval","settings","en","require-approval","Require approval before registration","Hold free-page sign-ups for your review, then approve or reject them before anyone is registered for the event.",[12,13],"Require approval captures registrations on Venue first. Visitors submit the form as usual, see a pending confirmation, and wait until you decide. Only an approval registers them for the event.","Use it when the guest list must stay curated: invite-only webinars, partner events, or any free page where an automatic enroll is too open. Paid registration keeps its own path and does not use this queue.",[15,18,22],{"text":16,"image":17},"Open your page in the builder, on step 4 · Settings. The “Require approval” block sits below the access rules (free pages only).","\u002Fsupport\u002Fregistration-approval\u002Fen\u002Fstep-1.webp",{"text":19,"image":20,"caption":21},"Turn on “Require approval”. New sign-ups stay pending: nobody is registered for the event until you decide.","\u002Fsupport\u002Fregistration-approval\u002Fen\u002Fstep-2.webp","You cannot turn the setting off while anyone is still waiting in the queue.",{"text":23,"image":24,"caption":25},"Open the Registrants tab. The approval queue lists pending and failed requests. Approve or reject one row, or bulk-approve a selection (or all pending).","\u002Fsupport\u002Fregistration-approval\u002Fen\u002Fstep-3.webp","Failed rows can be retried (with a limit) or discarded.",[27,28,29],"Approve one runs the same registration path as a normal free sign-up, including capacity and sessions, and enrolls the visitor on the page’s event platform when the event comes from a connector. Bulk approve runs in the background and shows progress on the Registrants tab.","Changing the linked event discards pending and failed rows in the queue: those submissions were captured for the previous event.","Unavailable while registrant retention is “Don’t store on Venue”: Venue needs a place to keep the pending form answers.","builder\u002Fsettings\u002FSettingsStep.vue · pages\u002F[id]\u002Fregistrants.vue · i18n wizard.settings.approval.* + registrants.approval*","August 28, 2026",[33,62,89],{"feature":34,"category":6,"locale":7,"slug":35,"title":36,"lede":37,"purpose":38,"steps":40,"notes":56,"generatedFrom":60,"updated":61},"page-access","access-and-privacy","Control access and privacy","Password-protect the page, set its visibility, redirect after registration, and cap sign-ups.",[39],"The Settings step gathers the page's access rules: who can find it (search-engine visibility), who can load it (password), where visitors go after they register, and how many people can sign up.",[41,44,47,50,53],{"text":42,"image":43},"Open your page in the builder, on step 4 · Settings. Each rule is its own block with its own switch.","\u002Fsupport\u002Fpage-access\u002Fen\u002Fstep-1.webp",{"text":45,"image":46},"In the visibility block, choose “Public” (crawlable and indexable by search engines) or “Unlisted” (hidden from search, reachable only via its direct link).","\u002Fsupport\u002Fpage-access\u002Fen\u002Fstep-2.webp",{"text":48,"image":49},"Turn on “Password protection” to require a password before the page loads, then enter it — at least 8 characters. The eye button reveals it.","\u002Fsupport\u002Fpage-access\u002Fen\u002Fstep-3.webp",{"text":51,"image":52},"Turn on “Redirect after registration” and enter a full https:\u002F\u002F URL to send registrants to your own page — or leave the switch off to show the in-page confirmation.","\u002Fsupport\u002Fpage-access\u002Fen\u002Fstep-4.webp",{"text":54,"image":55},"Turn on “Registration limit” to cap sign-ups: set the maximum with the slider or the field. Once the limit is reached, the page shows a “registration full” message instead of the form.","\u002Fsupport\u002Fpage-access\u002Fen\u002Fstep-5.webp",[57,58,59],"An unlisted page is still reachable by anyone with the link: it is not protection, only a way to keep it out of search engines.","The password must be at least 8 characters and the redirect URL must start with https:\u002F\u002F — otherwise publishing is blocked on the Launch step.","These settings apply on publish: check them before taking the page live.","SettingsStep.vue (step 4) · i18n wizard.settings.*","July 16, 2026",{"feature":63,"category":6,"locale":7,"slug":63,"title":64,"lede":65,"purpose":66,"steps":69,"notes":83,"generatedFrom":87,"updated":88},"api-keys","Create and revoke API keys","Issue workspace keys to call the Venue API from your own code — then revoke them when you no longer need them.",[67,68],"API keys let workspace admins authenticate to the Venue API with a Bearer token (`vk_live_…`). A key carries the same access as a workspace admin, so treat it like a password: create it when you need an integration, copy the secret once, and revoke it as soon as it is unused.","Endpoints, Try-it, and code samples live in the in-app API documentation (`\u002Fdocs`).",[70,73,77,79,81],{"text":71,"image":72},"Open Settings → API keys. Only workspace admins can manage keys.","\u002Fsupport\u002Fapi-keys\u002Fen\u002Fstep-1.webp",{"text":74,"image":75,"caption":76},"The list shows each key’s name, prefix (`vk_live_…`), dates, and status. Filter Active \u002F All to hide or show revoked and expired keys.","\u002Fsupport\u002Fapi-keys\u002Fen\u002Fstep-2.webp","Switch to All to see revoked or expired keys alongside active ones.",{"text":78},"Click “Create key”, give it a name (e.g. “Production integration”), pick an expiration (30 days, 90 days, 1 year, or never), then confirm.",{"text":80},"Copy the secret immediately — it is shown only once. Tick “I’ve saved this key somewhere safe” before closing. You can open “Try in API docs” to paste it into the docs Try-it panel (it stays in this browser only).",{"text":82},"To stop a key, click “Revoke” on its row and confirm. Any integration using that key stops working right away — this can’t be undone.",[84,85,86],"Never commit API keys to source control or share them in chat or tickets.","Expired keys stop working automatically; revoked keys stay in the All filter for audit.","Non-admins see the tab but cannot create or revoke keys — ask a workspace admin.","SettingsApiKeysTab.vue · useApiKeys.ts · i18n settings.apiKeys.*","July 21, 2026",{"feature":90,"category":6,"locale":7,"slug":90,"title":91,"lede":92,"purpose":93,"steps":96,"notes":106,"generatedFrom":110,"updated":111},"data-retention","Set how long registrant data is kept","Choose a retention window for the personal data collected through your pages — or keep none on Venue at all.",[94,95],"Registrant data retention controls how long the personal data your pages collect (a registrant’s email and their form answers) is kept on Venue. It is a single, workspace-wide setting: it applies to every page in the workspace, and only workspace admins can change it. A daily backend job permanently deletes anything older than the window you pick.","Use it to match your own privacy policy or a legal requirement — keep data as long as you need it, or store none of it on Venue and rely on Livestorm as the system of record.",[97,100,104],{"text":98,"image":99},"Open Settings → AI & privacy. Registrant data retention is the second card, below AI page generation.","\u002Fsupport\u002Fdata-retention\u002Fen\u002Fstep-1.webp",{"text":101,"image":102,"caption":103},"Open the “Keep registrant data for” dropdown and pick a window: Unlimited (the default), 2 years, 1 year, 6 months, or 3 months. The change saves as soon as you pick.","\u002Fsupport\u002Fdata-retention\u002Fen\u002Fstep-2.webp","Data older than the selected period is permanently deleted.",{"text":105},"To store no registrant personal data at all, choose “Don’t store on Venue” — only anonymized analytics counts are kept, and a warning explains what that means.",[107,108,109],"The setting is workspace-wide and admin-only: it applies to everyone, and members see it but can’t change it.","Data older than the window (email and form answers) is deleted permanently by a daily job — this can’t be undone, so shorten the window deliberately.","“Don’t store on Venue” keeps zero registrant personal data; only anonymized counts remain for analytics.","SettingsAiTab.vue · useWorkspace.ts setRegistrantRetention · i18n settings.workspace.retention.*","July 22, 2026",{"prev":113,"next":135},{"feature":114,"category":6,"locale":7,"slug":115,"title":116,"lede":117,"purpose":118,"steps":121,"notes":129,"generatedFrom":133,"updated":134},"members","team-members","See who has access to the workspace","Check who shares your pages, and how a teammate joins.",[119,120],"A workspace is shared: everyone in it sees the same pages, brands, templates and media library. The Team members tab is where you check exactly who that is, with each person’s role.","There is nothing to invite here. Membership is federated from Livestorm: anyone on your Livestorm team joins by connecting their own account to Venue.",[122,125],{"text":123,"image":124},"Open Settings → Team members. One row per person, with their email, role and join date.","\u002Fsupport\u002Fmembers\u002Fen\u002Fstep-1.webp",{"text":126,"image":127,"caption":128},"A teammate joins by signing in to Venue with their own Livestorm account — there is no separate invite to send. Their role follows Livestorm: a Livestorm host becomes a Venue admin.","\u002Fsupport\u002Fmembers\u002Fen\u002Fstep-2.webp","Roles are derived from Livestorm, so there is no invite button.",[130,131,132],"One row per PERSON, not per connected platform: a colleague who signed in with both Livestorm and Zoom appears once, with one role. The small logos next to their email show which platforms they connected.","Admins can change workspace settings — custom domain, API keys, Stripe, AI and data retention. Members build and publish pages.","The list is read-only: roles come from Livestorm, so change them there.","SettingsMembersTab.vue · useWorkspace.ts · i18n settings.members.*","July 28, 2026",null,[137,140],{"hreflang":138,"path":139},"fr","\u002Fsupport\u002Fparametres\u002Fexiger-une-approbation",{"hreflang":7,"path":141},"\u002Fsupport\u002Fsettings\u002Frequire-approval",{"connected":143},false,1787923385349]