For sessions that should not be readable by strangers
A password turns the registration page into a door with a lock on it: the URL may travel, but only people you have told can open the form. Here is what the gate covers, who tells guests the word, and what it deliberately cannot do.
The password sits on the page, in front of everything else. Someone with the URL who does not have the word faces the prompt: the session exists, but the agenda, the speaker details and the sign-up form stay behind it. That matters more than it sounds, because a page you would rather keep to guests still carries information the wider world might read — who is speaking, what is promised, who is expected.
It also changes who can register. On an open page anyone curious can leave a name; on a gated page the form only appears once the word is typed. The gate is not a bouncer checking identities, and nothing here verifies that a person is who they say they are. It is a shared secret, which is a simpler and more honest mechanism: whoever holds the word can open the form, and whoever you told holds the word.
One confusion is worth clearing before anything else, because the product has two separate mechanisms and guests feel both. The password guards the registration page. The access link guards the session: every person who registers gets their own private link in the confirmation email, which is the only dependable way into the room itself. A guest's evening passes through both doors in order — the word to sign up, their own link to attend.
So the password is not a substitute for the private link, and the private link does not make the password pointless. A gated page keeps curious strangers away from the form and the content. The per-attendee link keeps the session away from everyone who did not register, gated page or not.
The page does not email the password to anyone. Telling people is the host's job, and it pairs naturally with the invitation you are sending anyway.
You do, in the same message that carries the page link — an email to your list, a WhatsApp note to a named group, a line on a slide at the end of a call.
One sentence is enough: the page is locked, and the word you need is here. Guests should never have to guess that a link without a password is a broken link.
If the invitation goes somewhere broad, send the link there and the word through a channel only your invited list uses. Posting the password under the link gives the lock back to the crowd.
Because it is a shared secret, a password is only as private as the people holding it. A guest who passes the word to a colleague has, in effect, passed the page. There is no per-person key and no verification at the door, and we will not pretend otherwise. What covers the difference is the seat limit: set the number of places to the list you actually invited, and even a forwarded word runs into a full page rather than an open one. The password keeps the form off strangers' screens; the capacity decides what happens when they arrive anyway.
How it works
One webinar or workshop, its start time with a time zone label, agenda chapters and speaker. Keep it a draft while you work — an unpublished page is invisible to guests.
The gate is optional and lives on the page settings. Switch it on, and the form hides behind the prompt until someone types what you told them.
The page address goes into your invitation; the password travels with it to the invited names, or through a quieter channel when the invitation goes somewhere broad.
Each sign-up lands on your dashboard list as it happens, and every registrant gets their own access link for the session by email.
Questions
No, and both matter. The password opens the registration page; the access link is individual to each registrant and arrives in the confirmation email as the way into the session. They lock different doors, one after the other.
It does not. The gate exists on the page, and telling invited guests the word is part of sending the invitation. The confirmation email carries the attendee's personal access link, which is a separate thing.
They solve different problems, and the strong setup uses both. The password controls who can open the form; the seat limit controls how many registrations the page accepts. A shared word without a cap is still a shared word.
No. The password is only for opening the registration page beforehand. On the day, an attendee clicks the private link in their confirmation email, and the page password never comes up again.
Only sessions that are genuinely for a named group. The password is optional by design: a public session you want filled loses nothing from an open form, and a closed one gains quiet from the gate.
Get Started
Lock the page, send the word with the invitation, and let the seat limit stand behind it. The form opens for the guests you named and stays shut for everyone else.
