[{"data":1,"prerenderedAt":176},["ShallowReactive",2],{"support-article-settings-custom-domain":3,"ls-connection":174},{"article":4,"related":36,"neighbors":116,"alternates":168},{"feature":5,"category":6,"locale":7,"slug":5,"title":8,"lede":9,"purpose":10,"steps":13,"notes":28,"generatedFrom":34,"updated":35},"custom-domain","settings","en","Use your own domain","Serve your published pages on your own subdomain instead of the default Venue address.",[11,12],"By default a published page lives at venue.livestorm.app\u002Fyour-company\u002Fyour-page. Pointing your own subdomain at Venue keeps visitors on your brand, and keeps the SEO value of your pages on your own domain.","The domain is set once per workspace and applies to every published page in it.",[14,17,20,24],{"text":15,"image":16},"Open Settings → Custom domain. Only workspace admins can change it, since it affects every published page.","\u002Fsupport\u002Fcustom-domain\u002Fen\u002Fstep-1.webp",{"text":18,"image":19},"Enter a subdomain you control, for example events.acme.com, then click Add domain.","\u002Fsupport\u002Fcustom-domain\u002Fen\u002Fstep-2.webp",{"text":21,"image":22,"code":23},"The domain moves to “Awaiting DNS” and Venue shows the CNAME record to create at your DNS provider. Copy the target and add it as a CNAME for your subdomain.","\u002Fsupport\u002Fcustom-domain\u002Fen\u002Fstep-3.webp","venue.livestorm.app",{"text":25,"image":26,"caption":27},"Once the record has propagated, click “Check again” to activate the domain. Then choose what happens to the old default URL: keep both working, redirect it, or switch it off.","\u002Fsupport\u002Fcustom-domain\u002Fen\u002Fstep-4.webp","An active domain, with the default-URL behaviour set to “keep both working”.",[29,30,31,32,33],"Subdomains only (events.acme.com, go.acme.com). A root domain such as acme.com is refused: it needs an ALIAS\u002FANAME record that not every DNS provider offers.","DNS propagation can take a few minutes, sometimes longer. “Check again” is safe to click as often as you like.","One domain per workspace, and a hostname already claimed by another workspace is refused.","“Redirect” sends the old venue.livestorm.app links to the same page on your domain with a permanent (301) redirect, so existing links and their SEO value follow.","Removing the domain puts every page back on the default URL immediately.","SettingsDomainTab.vue · useWorkspace.ts · custom-domain\u002Fhostname.ts · i18n settings.domain.*","July 28, 2026",[37,66,93],{"feature":38,"category":6,"locale":7,"slug":39,"title":40,"lede":41,"purpose":42,"steps":44,"notes":60,"generatedFrom":64,"updated":65},"page-access","access-and-privacy","Control access and privacy","Password-protect the page, set its visibility, redirect after registration, and cap sign-ups.",[43],"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.",[45,48,51,54,57],{"text":46,"image":47},"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":49,"image":50},"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":52,"image":53},"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":55,"image":56},"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":58,"image":59},"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",[61,62,63],"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":67,"category":6,"locale":7,"slug":67,"title":68,"lede":69,"purpose":70,"steps":73,"notes":87,"generatedFrom":91,"updated":92},"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.",[71,72],"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`).",[74,77,81,83,85],{"text":75,"image":76},"Open Settings → API keys. Only workspace admins can manage keys.","\u002Fsupport\u002Fapi-keys\u002Fen\u002Fstep-1.webp",{"text":78,"image":79,"caption":80},"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":82},"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":84},"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":86},"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.",[88,89,90],"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":94,"category":6,"locale":7,"slug":94,"title":95,"lede":96,"purpose":97,"steps":100,"notes":110,"generatedFrom":114,"updated":115},"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.",[98,99],"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.",[101,104,108],{"text":102,"image":103},"Open Settings → AI & privacy. Registrant data retention is the second card, below AI page generation.","\u002Fsupport\u002Fdata-retention\u002Fen\u002Fstep-1.webp",{"text":105,"image":106,"caption":107},"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":109},"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.",[111,112,113],"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":117,"next":147},{"feature":118,"category":6,"locale":7,"slug":118,"title":119,"lede":120,"purpose":121,"steps":124,"notes":138,"generatedFrom":146,"updated":35},"paid-registration","Charge for registration","Require a one-time payment before a visitor is registered.",[122,123],"A paid page turns payment into the last gate before sign-up: nothing is created in Livestorm and no registrant is recorded until Stripe confirms the charge. Useful for paid masterclasses, workshops and training sessions.","The money goes to your OWN Stripe account (direct charges): you are the merchant of record, you own receipts, refunds and disputes, and Venue takes no cut.",[125,128,131,134],{"text":126,"image":127},"Paid registration needs a connected Stripe account. Open Settings → Integrations and check that the Stripe row reads “Connected”.","\u002Fsupport\u002Fpaid-registration\u002Fen\u002Fstep-1.webp",{"text":129,"image":130},"Then open your page in the builder, on step 4 · Settings. The Payment group sits below the access rules.","\u002Fsupport\u002Fpaid-registration\u002Fen\u002Fstep-2.webp",{"text":132,"image":133},"Turn on “Paid registration”. Until a Stripe account is connected and able to take card payments, the card stays greyed out with a link to Integrations.","\u002Fsupport\u002Fpaid-registration\u002Fen\u002Fstep-3.webp",{"text":135,"image":136,"caption":137},"Enter the price and its currency, then optionally a line-item label — it is what buyers see on the Stripe checkout and receipt. Leave it empty to fall back to the event title.","\u002Fsupport\u002Fpaid-registration\u002Fen\u002Fstep-4.webp","A €49 ticket labelled “Masterclass ticket”, ready to publish.",[139,140,141,142,143,144,145],"The minimum price is 0.50 in the selected currency (EUR, USD or GBP).","The price is snapshotted by the server when a visitor submits, so it cannot be tampered with from the browser — and changing it later never re-prices a sign-up already in progress.","Someone who is already registered is not charged again: the form recognizes their email and skips checkout.","On a multi-session page, one payment registers every session the visitor picked.","Refunds and disputes happen in your own Stripe dashboard, not in Venue.","If a payment succeeds but Livestorm cannot be reached, the Launch step lists those visitors under “paid but not registered” so you can refund them.","Disconnecting Stripe stops paid pages from taking payments until you reconnect.","builder\u002Fsettings\u002FSettingsStep.vue · SettingsPaymentsTab.vue · usePayments.ts · i18n wizard.settings.payment.*",{"feature":148,"category":6,"locale":7,"slug":149,"title":150,"lede":151,"purpose":152,"steps":155,"notes":163,"generatedFrom":167,"updated":35},"members","team-members","See who has access to the workspace","Check who shares your pages, and how a teammate joins.",[153,154],"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.",[156,159],{"text":157,"image":158},"Open Settings → Team members. One row per person, with their email, role and join date.","\u002Fsupport\u002Fmembers\u002Fen\u002Fstep-1.webp",{"text":160,"image":161,"caption":162},"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.",[164,165,166],"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.*",[169,172],{"hreflang":170,"path":171},"fr","\u002Fsupport\u002Fparametres\u002Fdomaine-personnalise",{"hreflang":7,"path":173},"\u002Fsupport\u002Fsettings\u002Fcustom-domain",{"connected":175},false,1787923385349]