How to Limit Form Submissions in WordPress

You set up a registration form, shared the link, and now your inbox is filling up with duplicate entries from the same person. Or maybe the opposite problem: you have 50 spots for a workshop and no way to make the form stop accepting signups when they’re gone.

Both situations are more common than they should be, and both have a clean fix in Ninja Forms. The built-in Restrictions settings let you cap total submissions, block duplicate entries, and restrict form access to logged-in users. No add-ons required.

This walkthrough covers all three controls so you can apply whichever one (or combination) fits your situation.

What You’ll Need

To follow along, you’ll need Ninja Forms (free). All three Restrictions controls covered here are built into Ninja Forms core.

Cap the Total Number of Submissions Your Form Will Accept

If you’re running an event registration, a limited-capacity offer, or any form where there’s a hard ceiling on responses, the Submission Limit setting closes the form automatically when that ceiling is reached. You set the number once and forget about it.

Here’s how to set it up:

1. Open your form in the Ninja Forms builder.
2. Click the Advanced tab at the top of the builder (alongside Form Fields and Emails and Actions).
3. Click into Restrictions to open the settings drawer on the right.
4. Find the Submission Limit field and enter your maximum number. For a 50-person workshop, enter 50. Leave it blank if you want no limit.
5. Find the Limit Reached Message field just below it and write the message visitors will see once the form closes. Something like: “Sorry, registration is now closed. All spots have been filled.”
6. Click Done in the top right, then save your form.

Once the limit is reached, the form is replaced entirely by your message. Visitors cannot see or interact with any fields. If you need to reopen spots later, deleting submissions frees up capacity automatically.

That covers the hard cap. But a cap alone doesn’t stop the same person from using up multiple spots before you hit it. That’s where the next approach comes in.

Prevent the Same Person from Submitting More Than Once

A submission limit stops the form when you hit capacity. It does nothing about someone submitting five times with five different names. The Unique Field setting handles that by checking each new submission against existing ones and blocking any duplicate value in the field you choose.

Email address is the most common choice because it’s both required and hard to fake at scale, but you can use any supported field type.

Here’s how to configure it:

1. In the Restrictions drawer (Advanced tab → Restrictions, as shown above), find the Unique Field dropdown.
2. Select the field that must be unique across submissions. For one-per-person enforcement, choose Email Address.
3. In the Unique Field Error Message box, write what someone sees if they try to submit again. Example: “This email address has already been used to register. Each person may only register once.”
4. Save your form.

When someone submits, Ninja Forms checks the database for any existing submission with the same value in that field. If it finds a match, the submission is blocked and the error message appears directly below the field. The form stays visible so the person can correct it if they made a typo.

A few things worth knowing about Unique Field:

• One field per form. You can designate only one Unique Field at a time.
• Phone fields are not supported. If you need to enforce uniqueness on a phone number, use a Single Line Text field with an input mask instead.
• The check is server-side. It cannot be bypassed by disabling JavaScript.

Between Submission Limit and Unique Field, most use cases are covered. But if your form is for members only, there’s a third control that can round things out.

Restrict the Form to Logged-In Users Only

Sometimes the right answer to “who can submit this form” is simple: only people with accounts on your site. The Logged In setting replaces the form with a message for any visitor who isn’t authenticated, before they even see the fields.

To enable it:

1. In the Restrictions drawer (Advanced tab → Restrictions), find the Logged In toggle and switch it on.
2. In the Not Logged-In Message field that appears, write what visitors should see. Example: “You must be logged in to register for this workshop.”
3. Save your form.

Anonymous visitors will see your message instead of the form. Logged-in users see the form normally and can submit without any additional friction.

Note that this setting is optional for most registration use cases. If your form is public but you want submission limits and duplicate prevention, Submission Limit and Unique Field are all you need. Logged In is best suited for member portals, internal tools, or any situation where unauthenticated access is never appropriate.

Stacking All Three Together

These three settings are designed to coexist. You can enable all of them on the same form and they won’t conflict. A realistic configuration for a members-only workshop with 50 spots: set Submission Limit to 50, choose Email Address as the Unique Field, and turn on Logged In for member-only access.

The practical result: only members can see the form, each member can register once, and the form closes automatically when all 50 spots are claimed.

You’ve now seen three approaches to limiting who can submit and how many times. Start with whichever one fits your use case. If your situation calls for it, layer them freely.