<?xml version="1.0"?><!-- generator="bbPress" -->

<rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
>

<channel>
<title>MachForm Community Forums Topic: Feature request - New Protection &#038; Limit option: user login required</title>
<link>https://www.machform.com/forums/</link>
<description>MachForm Community Forums Topic: Feature request - New Protection &#038; Limit option: user login required</description>
<language>en</language>
<pubDate>Sun, 03 May 2026 18:37:54 +0000</pubDate>

<item>
<title>Giorgio on "Feature request - New Protection &#038; Limit option: user login required"</title>
<link>https://www.machform.com/forums/topic/feature-request-new-protection-038-limit-option-user-login-required#post-16709</link>
<pubDate>Wed, 02 Jan 2013 22:15:29 +0000</pubDate>
<dc:creator>Giorgio</dc:creator>
<guid isPermaLink="false">16709@https://www.machform.com/forums/</guid>
<description>&#60;p&#62;In the form properties an additional method could be added to limit the number of entries:&#60;br /&#62;
- request user login before form can be filled out. &#60;/p&#62;
&#60;p&#62;This would be the only way to actually limit entries to a single physical person rather than to a client.&#60;br /&#62;
Of course this would require also a user registration feature, with minimum:&#60;br /&#62;
- email&#60;br /&#62;
- password&#60;/p&#62;
&#60;p&#62;It would be nice if the administrator could decide which additional fields are shown during user registration,&#60;br /&#62;
(could be for example: gender, year of birth, nationality, etc). This has also the advantage that these information&#60;br /&#62;
must not be inserted in each form.
&#60;/p&#62;</description>
</item>

</channel>
</rss>
