A yes, with the mechanics
Yes — and the limit is a stop, not a suggestion. The page counts names against the number you set, says so when the room is full, and offers late arrivals the waitlist rather than a dead end. What each of those does in practice.
The setting exists, and the honest way to describe it is that the page holds the line for you. Enter a number of places, and registrations count against it as names arrive. While seats remain, the page can show how many are left — a live nudge rather than a fine print. When the limit is reached, the page says plainly that it is full, and it does not take further names past the number.
The difference between an enforced cap and a polite note is what everything else rests on. A note asks people to respect the number; an enforced stop makes respect unnecessary. Nobody has to overbook a meeting room, apologise to late registrants, or explain why the fifty-first person was let in. The page already answered that before you had to.
The normal page — promise, agenda, speaker, form — with the seats-remaining line doing quiet work for the people who were deciding anyway.
A full page: closed rather than broken. The session still reads as real and worth an invitation; the form is simply finished, and the date tells them why.
If you turned it on, the page takes their name and email instead of refusing them entirely, tells them that an email comes if a place opens, and files them on your list with waitlisted status.
Cancellations are marked on your list with their status, so you can see the opening. The page never takes registrations past your number, and releasing a seat to the waitlist is the host's call, made from the list.
Rooms have sizes. Whatever platform you present on, the practical ceiling for a session that stays good — everyone seen, everything audible, your attention spread wide enough — is a real number, and the cap is how the registration side of the evening agrees with it. There is also a plainer reason to choose the number deliberately: an uncapped page fills itself to wherever the internet carries the link, and a large registered list with a small room produces apologies, not order.
Capping early is cheap and capping late is not. Decided before the invitations go out, a limit is just a setting. Decided afterwards, every change is a message to people who booked against the old number.
A cap counts registrations; your evening counts attendance. Those two numbers never match perfectly, and the product is candid about it — the list keeps attended and no-show statuses, marked by the host, and no mechanism verifies who was actually in the room beyond what you record. So the cap protects the platform's room from the sign-up side, and the statuses tell you afterwards how many chairs really sat someone. Hosts who plan around both — cap the room, watch the pattern of no-shows across sessions — set numbers that hold without leaving gaps.
One last honest note on the number itself: what can be set depends on the host's plan, so the right instruction is simply to cap sign-ups to the size of your room. The plan tiers and their limits are laid out on the pricing page rather than quoted here.
How it works
Start from the room you can genuinely serve on the platform you bring. That number goes on the page before the link goes anywhere else.
A single webinar or workshop: agenda chapters, speaker, start time with its time zone label, and the form that counts against the limit.
It is a switch on the page. On, the overflow becomes a list of real interest you can invite next; off, a full page is simply a full page.
The list updates as replies arrive, seats count down against the number, and the page itself announces when the room is full.
Questions
It stops. The seat limit is enforced: the page shows that places are left while they exist, says when it is full, and takes no further registrations past the number you set.
That is the waitlist, and it is the host's choice to turn on. Late arrivals add their name and email, are told an email follows if a place opens, and appear on your list marked waitlisted.
Cancellations are recorded with their status on your list, where you can see them. What the page guarantees is that it never accepts registrations beyond your number; moving a waitlisted name into a freed seat is a decision you make from the list.
Sign-ups, which is the only part a page can control. Who attends is recorded afterwards through the attended and no-show statuses the host marks, and the two numbers rarely match exactly.
The size of the room you can genuinely serve, not the biggest your platform allows. How high a limit you can set follows your plan; the comparison of plans lives on the pricing page, and no figure here would be honest without knowing which room you are in.
Get Started
Decide what room you can serve, set it before the first invitation, and let the full page say no in your stead. A capped list is a list you can plan around.
