To make an event registration form with a capacity limit in Notion, add a form to a Registrations database, count seats with a rollup, and subtract that count from a Capacity number with a formula. Notion forms have no built-in response limit, so the form won’t close itself. When the formula hits zero, you set the form to No access by hand.
Can a Notion form limit the number of registrations?
No. A Notion form can’t cap registrations on its own. Notion’s forms help describes three choices under Who can fill out: your workspace, Anyone on the web with link, and No access. It lists no response limit and no close date.
No access is the only off switch. Notion describes it as the option to pick “if you’d like to close your form and stop accepting new responses.” Our guide on how to close a Notion form walks through the menu.
What you need before you start
You need two databases and Full access to both. Forms, relations, rollups and formulas work on every Notion plan, so the counter itself costs nothing.
- Events: one row per event, with a
Capacitynumber property. - Registrations: one row per signup, filled in by the form.
- A relation between the two, so each registration points at its event.
For a single event, skip Events. Add a Seats number property to Registrations, hover the table footer, select Calculate, then More options, and choose Sum. Seats taken shows at the bottom of the table. The two-database version below pays off once you run more than one event.
How to build an event registration form with a capacity limit
Build the form first, then the counter on top of it. The steps below use a pottery workshop with 10 seats as the example.
- Create the
Registrationsdatabase and add a Form view. Ask for Name, Email and Seats (a number), and mark all three Required. Web forms are anonymous, so the name and email questions are the only way you’ll know who signed up. - Create the
Eventsdatabase. Add the workshop as a row and setCapacityto 10. - In
Registrations, add a relation property calledEventthat points atEvents. Limit it to 1 page so a signup can’t belong to two events. - In
Events, add a property, choose Rollup as the type, and name itSeats taken. Pick the relation toRegistrations, pick theSeatsproperty, and choose Sum as the calculation. - Add a formula property called
Spots left:
prop("Capacity") - prop("Seats taken")
- Add a second formula called
Status, so the row says in words what the number means:
if(prop("Spots left") <= 0, "Full", "Open")
- Open Share form, set Who can fill out to Anyone on the web with link, and send the link.
The steps for rollups come from Notion’s relations and rollups help. Its formula reference confirms that a formula can read a rollup, and that if returns the first value when the condition is true and the second when it isn’t.
Every new registration has to be linked to its event before the rollup counts it. On a paid plan, open the form builder’s ••• menu, choose Automations, and create one with the Page added trigger and the Edit property action to fill in Event. On the Free Plan, select the new rows in the Responses table and set Event in bulk. Test the automation with one fake signup before you share the link.
Count seats, not submissions
A capacity limit should count people, because one submission can bring more than one person. That’s why the rollup above uses Sum on Seats instead of Count all on the relation.
Take the pottery workshop. Four people register, and three of them bring a friend. Count all reports 4 and tells you 6 spots are left. Sum reports 7 seats taken and 3 spots left, which matches the chairs in the room.
If you never allow guests, drop the Seats question and use Count all.
Who closes the form when the event is full?
You do. Notion can tell you the event is full, but it can’t close the form. Notion’s database automations offer actions such as Send notification to, Send mail to and Send Slack notification to, and none of them changes a form’s sharing setting. Formulas can’t be used as triggers either, so you can’t fire an automation the moment Status turns to “Full”.
| Job | Works in Notion? | Plan |
|---|---|---|
| Count seats taken and spots left | Yes, with a rollup and a formula | Any |
| Alert you on every new registration | Yes, Page added trigger with a notification, mail or Slack action | Paid; the Free Plan allows Slack notifications only |
| Alert you only when the event is full | No, formulas can’t trigger automations | None |
| Close the form at capacity | No, set No access by hand | None |
So set up a Page added alert, check Spots left each time it fires, and switch the form to No access when it reads zero. Send mail to needs a Gmail account. Our post on Notion form automation covers the setup.
What to do when registrations go over the limit
Plan for overshoot, because a hand-closed form will sometimes take one signup too many. Someone registers while you’re asleep, or two people submit in the same minute.
Even tools with a real response limit have this problem. As of November 2026, Google Forms lets you choose After a number of responses under Set close date or response limit, yet its help page warns: “If multiple people respond at the exact same time, the form accepts responses regardless of the response limit.”
Use the form’s Confirmation body to tell people that seats are confirmed in order of signup, and that you’ll email if the event filled before their response arrived.
When it happens, sort the Responses table oldest first. Everyone past the capacity line goes on a waitlist. Our Notion waitlist form guide shows how to number the queue.
My take: always set Capacity a seat or two under the real room limit. Telling one person they’re on the waitlist is easy. Finding an extra chair on the day is not.
When a form tool with a built-in limit makes more sense
A manual close stops being reasonable when seats cost money or the link will spread fast. For paid events, let the payment tool enforce the limit, as described in our workshop registration form guide.
Some third-party Notion form builders offer a submission cap as a paid feature that closes the form automatically at the limit. Check whether that cap counts submissions or people before relying on it. A cap on submissions brings back the plus-one problem.
Our own product has the same limitation. nDBForms doesn’t list a capacity limit or a scheduled close among its features. Each submission becomes a row in your Notion database, so the rollup and formula above work the same way with it, and you get an email notification for each new submission. You still close the form yourself.
FAQ
Can a Notion form close automatically when the event is full?
No. Notion’s forms help lists no response limit or close date, and its automations have no action that changes a form’s sharing setting. Someone with Full access has to set Who can fill out to No access.
How do I count plus-ones against the capacity?
Add a required Seats number question to the form and make the rollup on the Events database use Sum on Seats. A registration for two people then takes two seats, not one.
Do I need a paid Notion plan for a capacity limit?
Not for the counter. Forms, relations, rollups and formulas work on every plan. Automations that notify you by email or in Notion need a paid plan. The Free Plan can only create Slack notification automations.
Can the form show how many spots are left?
Not as a live number. Question descriptions and the confirmation text are fixed text you type, so the spots-left figure lives in your database. Update the form description by hand when seats run low.