By default anyone with the link can answer a form. When the answers should come from known people, switch Who can respond in the builder under Settings > Access & limits. You can change it any time; it applies to new visits straight away.
| Mode | Who gets in | How they prove it |
|---|---|---|
| Anyone with the link | Everyone | Nothing |
| Anyone who confirms their email | Anyone who owns an address | A one-time code sent to that address |
| Only invited email addresses | Addresses and domains on your list | The same one-time code, sent only if the address is on the list |
| Only signed-in members of this workspace | People in your Formspring workspace | Their Formspring sign-in |
| Only members signed in through single sign-on | Workspace members whose address is covered by your enforced single sign-on | Their company sign-in |
One-time codes
A code works once, for 15 minutes, and a new request replaces the older code. Five wrong guesses lock that code. Respondent sessions last 12 hours and belong to one form only: a session for one form never opens another.
The first screen answers the same way whether or not an address is invited, so nobody can use it to find out who is on your list.
If a code is wrong, expired or already used, the respondent sees one clear message and a Send a new code button next to Use another address. Nothing else is needed to get back in.
Invited addresses
Paste one entry per line: a full address such as ada@example.com, or a whole domain such as @yourcompany.com. The list can hold 500 entries and is never shown on the public page. Over the API it is the access_allowlist field of a form.
Workspace and single sign-on modes
These modes do not send a code. The respondent opens the form, and if they are signed out they are asked to sign in and then returned to the form. Someone signed in to a different workspace sees that the form is not open to their account and can sign in with another one; they never see answers.
The single sign-on mode additionally needs an enabled, enforced single sign-on connection with a verified domain on your workspace (see Teams > Single sign-on). Members whose address is outside that domain are refused.
These two modes use the respondent's Formspring session, so they work on the hosted form page. For a form embedded on another website the browser may not share that session; use confirmed email or invited addresses there.
What is protected
The same check guards submitting, saving a draft, starting an in-form payment and reopening a response to edit it. Opening a saved edit link on a restricted workspace form also needs the right sign-in, so a forwarded link is not enough.
Over the API and MCP
PUT /api/v1/forms/{form}acceptssettings.access_mode(public,verified_email,invited,workspace,sso) andaccess_allowlist.GET /api/v1/forms/{form}returnsrespondent_accesswith the mode and, for invited forms, the list.- The
update_formtool takes the same fields.
What's next
- Saved drafts and edits → - resume later and change answers afterwards
- Form builder → - where the settings live
