When the guest list is fixed and the link is not
Invite-only is not a single switch — it is an arrangement: a link sent only to the list, a seat count set to the exact headcount, and a page that says closed when the room is full. How the pieces combine, and what they honestly leave open.
One sentence covers what an invite-only session is trying to do: everyone in the room was on the list, and nobody off it arrived by accident. It is worth saying up front that no single setting delivers this, and no mechanism checks a name at the door. There is no approval step in the registration flow that you should rely on; a sign-up counts when it lands.
What does deliver the goal is an arrangement of ordinary controls, and understanding that they are ordinary is what makes the room hold. A closed webinar is built from distribution, capacity, and a gate — not from a lock with names on it.
The page URL goes to the list and nowhere else. There is no directory to appear in, so an unshared page is as unfindable as a card that was never printed.
Set the limit to the number you invited. From that moment the list and the room cannot disagree: anyone uninvited either occupies a seat meant for a guest, or meets the full page.
Optional, and the blunt half of the arrangement. The word goes to the invited names only, so even the form itself stays out of reach of anyone who finds the link.
Turned on, late arrivals leave their details instead of forcing their way in or vanishing. Turned off, they meet a closed page. Either way the number you set holds.
When the seats are gone, the page says so plainly — and while places remain it can show how many are left. For a normal session this is logistics. For an invite-only one it is the moment the design proves itself: the forwarded link, the well-meaning plus-one, the colleague of a colleague, all reach a page that has already stopped taking names. Nothing has to be policed after the fact because the count did it first.
Watch the list as the days run. Registered names arrive, cancellations are marked, and the statuses — registered, attended, waitlisted, cancelled, no-show — tell you the real shape of the room before the session starts.
Honesty is part of the setup, because hosts who expect a bouncer get surprised. There is no identity verification, no single sign-in, no per-guest permission of any kind. A guest who passes the password and the link to someone off the list, while seats remain, has effectively added that person to the list. The mechanisms shrink that window — seats at exact headcount mean every extra body displaces an invited one, which is visible and stoppable — but the social layer is the one holding the door, and it always was.
How it works
Agenda chapters, speaker, start time with its time zone label, the questions you want answered. Keep it in draft while the list itself is still being written.
Seats to the headcount invited, the password switched on, the waitlist chosen. Do all of it before publishing, so the page opens already holding the line.
The link and the word travel together, by email or WhatsApp, to named people. Broad posts are not part of an invite-only plan.
Names arrive against the cap and statuses sort themselves as things change. A message to the registered segment closes the loop before the session starts.
Questions
Not one you should build a plan around — registrations count as they arrive, and nothing checks them first. A closed list is held by the seat count, the password and careful distribution instead.
With a password on the page, a prompt they cannot answer. Without one, the real form — until the seats run out, at which point the page says it is full, and the waitlist if you turned one on.
Because it converts every uninvited sign-up into a visible displacement. A seat taken by a stranger is a seat an invited guest cannot hold, and a page capped at your list makes that trade happen in the open rather than on the night.
They protect different things. The cap protects the room size; the password protects the page content and keeps your list from filling with names you never meant to admit. A strictly closed session wants both.
Get Started
Send quietly, cap at the headcount, gate the form, and let the full page say no so you never have to. The list you invited is the room you get.
