Most forms are open to anyone with the link. For situations where you need a verified identity on every submission — internal feedback, employee policy acknowledgements, vendor onboarding, regulated workflows — NueForm lets you require respondents to sign in before they submit. There are two related toggles, and a separate companion feature called My Responses that gives every signed-in respondent a private list of everything they've submitted.
What "Require respondent login" Does
Open your form in the builder, expand the Form Login section in the right-hand settings panel, and turn on Require respondent login.
When this is on:
- Respondents who open the form see a sign-in screen instead of the first question. They can sign in with email + password, with Google / Microsoft / GitHub / Apple, or via SSO if their team uses it.
- New respondents can also create an account from the same screen.
- Once authenticated, the form opens normally and they see a small "Submitting as {your name}" header at the top so it's clear which account the submission will be tied to.
- After submission, the form owner sees the respondent's name and email on every response — both in the response detail view and in CSV exports, webhooks, and the public API.
- The submission is automatically saved to the respondent's My Responses page (see below), so they can come back to it later.
This is the right setting any time you need to know — and prove — who answered. Examples:
- Compliance acknowledgements ("I have read and agree to the policy")
- Internal employee surveys where anonymity isn't desired
- Vendor onboarding intake
- Beta-tester feedback when you want to follow up
Turning on "Require respondent login" is honest with the respondent. The sign-in screen explicitly tells them: "This form requires you to sign in before submitting. The form owner will see that you submitted this response." No hidden tracking — they choose.
How "Require team SSO" Interacts
If your form belongs to a team and that team has SSO configured, a second toggle becomes available: Require team SSO. It only appears when:
- The form is owned by a team (not a personal form), and
- That team has SSO set up under team settings.
When you turn on Require team SSO (which automatically enables Require respondent login as well):
- Only members of your team's identity provider can submit. Respondents who try to sign in with a personal email — even one that already has a NueForm account — will be turned away.
- The sign-in screen hides social and password options. The respondent only sees the SSO button.
- After they authenticate through your IdP, the form gate also confirms they are a current member of your team. If your team's auto-join setting is on, brand-new SSO users join your team at the role you've configured (default: viewer) and see the form. If auto-join is off, they see an "Approval required" page and need a team admin to invite them first.
- The form owner sees a
✓ SSObadge next to the respondent's name on every submission, confirming that the identity came from your trusted IdP.
This is the right setting for forms that should never leave your organization: internal-only intake forms, audit checklists, restricted feedback channels.
Require team SSO is more restrictive than just Require respondent login. A respondent who's already signed in to NueForm with a personal account but isn't on your team will be blocked. Make sure you actually want that strictness before turning it on — otherwise plain "Require respondent login" is enough.
What Respondents Get: My Responses
Every signed-in NueForm user has a My Responses page in their app sidebar (between Fuse and Analytics). It lists every form, contract, and Fuse activity they've submitted while logged in, with the most recent at the top. Respondents can:
- Search by form name.
- Filter by type — forms, contracts, or Fuse.
- Click into any past response to see exactly what they answered.
- Re-download signed contract PDFs (subject to the form owner's revocation status).
This is fully private. Only the respondent sees their own list — no one else, including team owners or NueForm staff, can see it. It's free on every plan, including the free tier.
There are two ways a response lands on My Responses:
- Automatically, when the form had Require respondent login turned on. Logging in is the entry condition, so the response is saved as a matter of course.
- By consent, when the form was open (no login required) but the respondent happened to be signed in to NueForm at submit time. After submission, NueForm asks: "Save this response to your My Responses page?" If they say yes, the response is added to their list. If they dismiss, nothing is saved on their side.
Respondents cannot delete entries from My Responses — it's a read-only history. (We may add deletion in a future update.)
Privacy Contract
NueForm draws a clear line between owner-visible identity and personal record:
| What happened at submit | Form owner sees identity? | Respondent's My Responses? |
|---|---|---|
| Form had Require respondent login on (with or without team SSO) | Yes — name, email, optional SSO badge | Yes — auto-saved |
| Form was open, respondent was signed in and clicked Save to My Responses | No — owner sees "Anonymous" | Yes — saved by consent |
| Form was open, respondent was signed in and dismissed the prompt | No — anonymous | No — nothing saved |
| Form was open, respondent was not signed in | No — anonymous | No — nothing saved |
The key thing: a consent-saved response is private to the respondent. The form owner never retroactively learns who submitted. The owner only sees identity for responses where the form explicitly required login at the time of submission — and the respondent saw that requirement before they signed in.
For contract-style forms where one signer's view of another signer's filled fields is restricted (the "hide other signers" setting), the same restriction applies on My Responses: a respondent only ever sees their own contributions, never another signer's private details.
Auto-Join and Team SSO
If you're a team admin and you've enabled SSO for your team, two related controls in the Members tab of your team settings determine how new SSO logins behave:
- Auto-add SSO members to this team. When on, anyone who signs in via SSO with an email at your team's domain is automatically added to your team at the configured default role (default: viewer). Each new auto-added member counts as a billable seat above your plan's included count.
- Require SSO for users at {your domain}. When on (the default for newly enabled team SSO), people with an email at your team's domain cannot sign in with a password or social provider — they must use SSO. This prevents the situation where someone with
name@yourcompany.comhas a personal NueForm account that isn't tied to your team. - Default role for new SSO members. Choose the role new auto-joined members start with. We default to viewer (read-only), and you promote intentionally as people take on more responsibility.
If auto-join is off, brand-new SSO logins from your team's domain are blocked at sign-in. The respondent sees an "Approval required" page asking their team admin to invite them. This applies to form-respondent SSO too — if your form has Require team SSO on, the same block applies. So if you want external-but-trusted SSO users to be able to fill in your team's restricted forms, make sure auto-join is on.
Summary
- Require respondent login = "I want to know who submitted this, and let them keep a copy on their My Responses page."
- Require team SSO = "Only members of my team, authenticated through my company IdP, may submit."
- My Responses = a free, private, per-user history of submissions — auto-populated for required-login forms, opt-in for open forms.
- The form owner only learns the respondent's identity when the form required login at submit time. Consent-saved responses stay anonymous to the owner.
- New SSO respondents flow through the team's auto-join + ssoEnforced settings — keep auto-join on if you want external SSO users to be able to fill in restricted forms without manual invites.
Related
- Teams — Team roles, seats, and SSO configuration
- Complete Team Setup Guide — End-to-end team setup, including SSO and access controls
- Audit Log — Track team activity (Enterprise)