Control access and privacy

Updated September 9, 2026

Password-protect the page, set its visibility, redirect after registration, and cap sign-ups.

What it’s for

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.

  1. Open your page in the builder, on step 4 · Settings. Each rule is its own block with its own switch.

  2. In the visibility block, choose “Public” (crawlable and indexable by search engines) or “Unlisted” (hidden from search, reachable only via its direct link).

  3. Turn on “Password protection” to require a password before the page loads, then enter it, at least 8 characters. The eye button reveals it.

  4. Turn on “Redirect after registration” and enter a full https:// URL to send registrants to your own page, or leave the switch off to show the in-page confirmation.

  5. 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.

Good to know

  • 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://. 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 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.

Related articles

Still need help?

Ask AI for a docs-grounded answer, or talk to our team.

Was this article helpful?