You can’t limit a Notion form to one response per person with a setting, because Notion has no response cap or duplicate check. What you can do is spot repeats: workspace-only forms record each respondent’s name, and a grouped view shows anyone who answered twice. To actually block a second submission, you need a form tool with a duplicate check, or a sign-in based form.
Does a Notion form support one response per person?
A Notion form doesn’t support one response per person, because its settings have no response limit of any kind. Notion’s forms help covers questions, sharing, anonymous responses, conditional logic and automations. It never mentions limiting responses per person or catching duplicates.
The closest setting does something else. Multi-select, relation and people questions take a maximum number of selections per response, which caps choices inside one answer. It doesn’t count submissions.
Setting access to No access stops all new responses, for everyone. See how to close a Notion form.
Who Notion records as the respondent
Notion records a respondent’s name only when the form is shared inside your workspace and anonymous responses are off. New forms get a Respondent property automatically. Forms built on an existing database use Created by instead.
Sharing decides what you see:
| Sharing setting | Who can answer | Name recorded? |
|---|---|---|
| Anyone at your workspace with link | Workspace members, plus guests with database access | Yes, if anonymous responses are off |
| Workspace link with anonymous on | Same people | No |
| Anyone on the web with link | Anyone, including people without Notion | No, always anonymous |
The last row is the catch. Notion’s help says respondents for public forms “will automatically be anonymous.” On a public signup, feedback survey or application, Notion can’t tell you who sent what. The guide to anonymous Notion forms covers the trade-off.
Spot repeat responses with a grouped view
A grouped view is the practical way to enforce one response per person in Notion after the fact. You can’t stop the second submission, but you can find it in seconds and decide which row to keep.
For a workspace-only form:
- Open the database behind the form.
- Add a new table view called Duplicates check.
- Open View settings, choose Group, and pick Respondent (or Created by). Notion’s grouping help says the database “will now group by values of that property.”
- Scan for any group with more than one row.
On a public form, add a required email question and group by that instead. Anyone can type a different address, so it proves nothing. Honest repeat submitters mostly reuse their own email, though.
Take a team lunch order form in a workspace. Priya submits Monday morning, changes her mind, and submits again at noon. Her group shows two rows. Someone deletes the older one and the kitchen count is right.
If people resubmit mostly to fix mistakes, let them edit instead. Workspace-only forms with anonymous responses off can give respondents access to their own response. See editing a Notion form response.
How other form tools enforce the limit
Other form tools enforce one response per person by tying each submission to an identity: an account, an email, a browser or a network. Each method has a different weak spot.
Google Forms has a Limit to 1 response toggle under Settings, next to Responses. Google’s help page says that with it on, “users must sign in to their Google Account” to fill out the form. That’s strong, but it shuts out anyone without a Google account.
Tally, as of November 2026, offers a duplicate check that’s free for all users. Its help page says you can use “any form field as the unique identifier,” plus IP address or a respondent ID stored in the browser. It also admits that “not all options are 100% bulletproof.”
| Method | How it identifies a person | How it gets bypassed |
|---|---|---|
| Account sign-in | A logged-in account | A second account |
| Email field | The address typed in | Typing a different address |
| Browser ID | Local storage in the browser | Another browser, device or incognito mode |
| IP address | The network | Another network or a VPN, and it blocks people on shared Wi-Fi |
Where nDBForms fits
nDBForms writes each submission as a new row in your Notion database, with an email question type, an email notification per submission and CSV export. Its published feature list doesn’t include a one-response-per-person setting or a duplicate check, so it won’t block a second submission.
It does make the after-the-fact check easy. Add a required email question and group the Notion database by it; every repeat shows up as a group with extra rows. If hard blocking decides it for you, test a tool with a duplicate check first.
Which approach to pick
The right approach depends on how much a duplicate actually costs you. For most internal forms, a grouped view and a quick weekly check is enough.
- Internal team form: keep it workspace-only, anonymous off, and group by Respondent.
- Public feedback or signups: add a required email question and group by it.
- Votes, giveaways or limited seats: use a sign-in based limit. Some people will drop off.
My take: don’t chase a perfect block on a public form. A determined person beats every method in the table above, and the strict ones cost you honest respondents. Collect everything and clean up with a grouped view. The limitation is time: this only works while you can still review the rows by hand. If spam is the actual problem, see stopping spam on a Notion form.
FAQ
Does Notion have a Limit to 1 response setting like Google Forms?
No. Notion’s forms help doesn’t describe any limit on responses per person or any duplicate check. You can close a form entirely, but not cap how often one person submits.
Can I see who submitted a Notion form?
Only for workspace-only forms with anonymous responses turned off. Notion fills a Respondent property, or Created by on an existing database, with the person’s name. Forms shared to anyone on the web are always anonymous.
Can people get around a one-response limit?
Usually, yes. Browser-based checks fail in a different browser or incognito mode, IP checks fail on another network, and email checks fail if someone types a different address. Google’s sign-in limit is the hardest to dodge, but a second account still works.
How do I remove duplicate responses in Notion?
Group the database by the Respondent or email property, look for groups with more than one row, and delete or archive the extra rows by hand. Notion forms have no built-in duplicate check.