Two URLs, and only one of them is public
The address you advertise and the address that opens the session are two different links, and confusing them is how private rooms leak. Where each one belongs in the attendee's evening, and what happens when either travels further than planned.
This is the link you put in emails, group chats, posts and the final slide of last session. It opens the invitation: the promise of the hour, the agenda chapters with their durations and takeaways, the speaker and their title, the start time wearing its time zone label, and the form asking a name and an email. Everything public about your webinar hangs off this address, and it should be as public as your promotion needs.
What it deliberately does not carry is the way into the room. Your join URL from your platform goes into the page settings and stays out of sight on the page itself, because a meeting address printed on a shared page is only shared with everyone.
When a name lands on the form, the confirmation email that goes back carries something the public page never shows: a link belonging to that registrant alone. That is the access route, and it works in the guest's favour twice over. They always have the way in at hand, in the mailbox they check; and the host knows that the set of people who can attend matches the set who registered, name for name.
The confirmation email is also where the small practical extras live — an .ics calendar file and a Google Calendar link sit there beside the access route, for the attendee to use or ignore. Nothing syncs anywhere by itself, and no meeting is created on your behalf; the file and the link simply make the date easy to hold onto.
A stranger finds a genuine invitation and can register if seats remain. That is the system working: a registration is a request to attend, logged on your list, not a door into the room.
Whoever opens it reaches the session. One person's link shared once is a choice by one person on your list — the failure mode is limited in a way a broadcast join address never is.
This is the most common problem and it has a host-side answer: you can broadcast a message to the registered segment of your list. The fix travels to the people who need it without the address going back onto a public page.
Put together, the two links let a host do two things that usually conflict: advertise freely and stay private. The registration page exists to be shared — the wider the better, since every name it collects is someone you chose to confirm. The room exists to hold the line at that list. A single link could not do both jobs, which is why the sessions that leak are almost always the ones that made one URL carry them.
One more consequence worth knowing: because a page carries one session, an access link belongs to one session too. A second date needs a second page, and its registrants get links that open only that second evening.
How it works
From email, chat or slide, the shared address leads to the real invitation and the registration form.
The answer lands on your list and counts against the seat limit you set before publishing.
It carries their own access link plus the calendar file and Google Calendar link — the whole attendee kit, in one email they keep.
On the day, email reminders arrive at 24 hours, 1 hour and 15 minutes unless the host switched them off, and the session opens from the private link, whatever platform it runs on.
Questions
No. Each registration generates its own link and delivers it individually in the confirmation email. That is the difference between an access route and a broadcast address.
It does not. The public page carries the session details and the form. The way into the room is delivered one person at a time, in the email that confirms their seat.
The colleague gets in. The mechanism prevents the broadcast — the join address copied into a group and scattered from there — not a deliberate share by one named registrant, which at least stays traceable to a name on your list.
Nothing syncs. The confirmation email brings an .ics file and a Google Calendar link the attendee can use, and the reminders are plain emails timed before the start. No account is connected and no meeting is created for them.
No — a page carries one webinar, and its access links lead only to that session. Running the same workshop on a second date means a second page with its own registrations and its own links.
Get Started
Share the registration link from every rooftop, and keep each attendee's way in where it belongs — in their own confirmation, for their own seat.
