Sharing a form is easy. Making sure the right people — and only the right people — can access it is a different story.

With this update, Walla gives you much more control over who can open your form, how often they can respond, and where the form can be accessed.

Verify respondents by email or phone

Respondent verification is no longer limited to email.

You can now require respondents to verify themselves using a code sent to their email address or phone number before they can access your form.

Need to restrict a form to a specific audience? You can allow only selected email addresses, entire email domains, or predefined phone numbers.

It’s a simple way to keep internal surveys internal, limit registrations to invited participants, or run forms for a predefined group without creating separate accounts for every respondent.

Or keep it simple with a password

Not every form needs individual verification.

You can also require respondents to enter a pre-shared password before accessing a form — useful for events, private communities, internal programs, or any audience that can share a common access code.

The verification screen is customizable, too. Add your own instructions so respondents know why verification is required, what they need to do, or who to contact if they have trouble accessing the form.

Stronger duplicate response prevention

Duplicate response prevention now works together with respondent verification.

You can limit submissions to one response per verified email address or phone number, giving you a much more reliable way to prevent repeat participation.

For votes, applications, internal surveys, or campaigns where one person should only respond once, you now have a stronger identity-based way to enforce that rule.

Keep embedded forms inside your website

If your Walla form lives inside your website or product, it can now stay there.

With Embed-Only Access, you can block direct access to the form URL and allow responses only when the form is embedded on an approved website.

For more advanced use cases, Enterprise teams can require signed tokens from their host server and even pass a member ID to Walla, allowing one-response-per-member restrictions without asking users to verify their email or phone again.

It’s especially useful for member-only pages, internal portals, and forms built directly into your own service.

Control who gets in, how many times they can respond, and where your form can appear.

Share your forms without giving up control over access.