[{"data":1,"prerenderedAt":135},["ShallowReactive",2],{"ls-connection":3,"support-article-settings-access-and-privacy":5},{"connected":4},false,{"article":6,"related":44,"neighbors":127,"alternates":129},{"feature":7,"category":8,"locale":9,"slug":10,"title":11,"lede":12,"purpose":13,"steps":15,"notes":33,"generatedFrom":42,"updated":43},"page-access","settings","en","access-and-privacy","Control access and privacy","Password-protect the page, set its visibility, redirect after registration, and cap sign-ups or close them at a set date.",[14],"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, how many people can sign up, and until when.",[16,19,22,25,28,31],{"text":17,"image":18},"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":20,"image":21},"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":23,"image":24},"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":26,"image":27},"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":29,"image":30},"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, unless you also turn on “Waiting list”, nested under the limit, which keeps the form open and queues whoever it would have turned away.","\u002Fsupport\u002Fpage-access\u002Fen\u002Fstep-5.webp",{"text":32},"Turn on “Registration close date”, under the limit, to stop sign-ups at a date and time of your choice, set in the event’s time zone (named next to the fields). Until then, the page shows “Registration open until” and the date under the form button. After it, the form gives way to a “registration closed” message that names the date.",[34,35,36,37,38,39,40,41],"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.","The “Waiting list” switch appears under the registration limit on free pages only, and is unavailable while registrant retention is set to “Don’t store”. See “Keep a waiting list when the page is full”.","The first date offered is 6:00 PM on the eve of the page’s last session, or tomorrow at 6:00 PM if that evening has passed or no session is ahead. A date already past closes registration on a published page at once, and the field says so.","To keep the date off the page, select the registration form on step 3 · Design and turn off “Show the closing date” in its properties. The message shown once registration has closed still names the date.","Anything already under way still completes after the close date: you can approve pending requests and promote people from the waiting list, and a payment started before the date goes through.","The same card carries “Email domain restrictions”, which decides whose address may register at all. See “Restrict which email domains can register”.","These settings apply on publish: check them before taking the page live.","builder\u002Fsettings\u002FSettingsStep.vue (step 4) · builder\u002Fsettings\u002FRegistrationLimitSetting.vue · builder\u002Fsettings\u002FRegistrationCloseSetting.vue · i18n wizard.settings.*","October 4, 2026",[45,72,95],{"feature":46,"category":8,"locale":9,"slug":46,"title":47,"lede":48,"purpose":49,"steps":52,"notes":66,"generatedFrom":70,"updated":71},"api-keys","Create and revoke API keys","Issue workspace keys to call the pages API from your own code. Revoke them when you no longer need them.",[50,51],"API keys let workspace admins authenticate to the pages 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`).",[53,56,60,62,64],{"text":54,"image":55},"Open Settings → API keys. Only workspace admins can manage keys.","\u002Fsupport\u002Fapi-keys\u002Fen\u002Fstep-1.webp",{"text":57,"image":58,"caption":59},"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":61},"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":63},"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":65},"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.",[67,68,69],"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":73,"category":8,"locale":9,"slug":73,"title":74,"lede":75,"purpose":76,"steps":79,"notes":89,"generatedFrom":93,"updated":94},"data-retention","Set how long registrant data is kept","Choose a retention window for the personal data collected through your pages, or have your pages keep none at all.",[77,78],"Registrant data retention controls how long the personal data your pages collect (a registrant’s email and their form answers) is kept. 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 have your pages store none of it and rely on your Livestorm events as the system of record.",[80,83,87],{"text":81,"image":82},"Open Settings → AI & privacy. Registrant data retention is the second card, below AI page generation.","\u002Fsupport\u002Fdata-retention\u002Fen\u002Fstep-1.webp",{"text":84,"image":85,"caption":86},"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":88},"To store no registrant personal data at all, choose “Don’t store”. Only anonymized analytics counts are kept, and a warning explains what that means.",[90,91,92],"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” keeps zero registrant personal data; only anonymized counts remain for analytics.","SettingsAiTab.vue · useWorkspace.ts setRegistrantRetention · i18n settings.workspace.retention.*","September 9, 2026",{"feature":96,"category":8,"locale":9,"slug":97,"title":98,"lede":99,"purpose":100,"steps":103,"notes":119,"generatedFrom":125,"updated":126},"data-requests","personal-data-request","Handle a personal data request","Find everything your workspace stores about one email address, download it as JSON, or erase it.",[101,102],"When someone asks what you hold about them, or asks you to delete it, Data requests answers for the whole workspace at once. Type their email address to search every page and campaign: registrations, approval requests, checkouts, campaign invitations, the campaign emails sent to them, and whether they opted out of campaign emails. You don’t need to know which page they signed up on.","Only workspace admins can use it. Members see the section with a note that it is reserved for admins.",[104,107,110,114,117],{"text":105,"image":106},"Open Settings → AI & privacy and scroll to Data requests, the last section of the tab, below Registrant data retention.","\u002Fsupport\u002Fdata-requests\u002Fen\u002Fstep-1.webp",{"text":108,"image":109},"Type the person’s email address and click Search. Capital letters and spaces around the address make no difference.","\u002Fsupport\u002Fdata-requests\u002Fen\u002Fstep-2.webp",{"text":111,"image":112,"caption":113},"The summary counts the records of each kind held for the address, lists the pages and campaigns they come from, and says whether the address opted out of campaign emails. Click “Download JSON” to save all of it to a file: that is the export to send for an access or portability request.","\u002Fsupport\u002Fdata-requests\u002Fen\u002Fstep-3.webp","If the workspace holds nothing for the address, the section says so instead.",{"text":115,"image":116},"To delete it, click “Erase all data”.","\u002Fsupport\u002Fdata-requests\u002Fen\u002Fstep-4.webp",{"text":118},"In the confirmation, retype the address and click “Erase permanently”. The section then lists what was deleted.",[120,121,122,123,124],"Erasing can’t be undone. It deletes every registration, approval request, checkout, campaign invitation and campaign email record held for the address, across all pages and campaigns, in one go. If the person also asked for a copy, download the JSON first.","Copies held by your connected provider (Livestorm, Zoom, Teams) are not affected. Handle those in the provider itself.","An address that opted out of campaign emails stays opted out after an erasure, so the person gets no more campaign emails. The opt-out is kept as a hash, not as the address itself.","Audit log entries that named the address keep the event but show the address masked (like j***@acme.com). The erasure is logged too, with the address masked.","A search returns at most 500 records of each kind. When an address goes past that, the summary warns you and the download only holds the first 500 of each.","SettingsDataRequestsSection.vue · useDataSubjects.ts · i18n settings.privacy.*","September 23, 2026",{"prev":128,"next":45},null,[130,133],{"hreflang":131,"path":132},"fr","\u002Fsupport\u002Fparametres\u002Facces-et-confidentialite",{"hreflang":9,"path":134},"\u002Fsupport\u002Fsettings\u002Faccess-and-privacy",1792141117659]