The registration behaviour screens are shown below. These parameters are each explained briefly.
Close registrations: If this value is set to "Yes", no registrations will be accepted for this event. If you are using features like password or time-based mechanisms to "auto-open" registrations, this value must still be set to "Yes". No registrations of any sort will be accepted if this is set to "No". The system administrator will have the option to over-ride this setting however.
Registration open to the Public?: This setting controls whether by default, non-logged in web-site users have visibility to this event. Normally this will be set to "Yes".
Maximum registrants: If a on-zero value is set, registrants will be "capped" at a particular threshold. This feature should not be used for camp, class or resource reservations since these event types already have a more sophisticated ability to limit registrations based on selections.
Notify on registration: Indicate whether the system should send an e-mail when new registrations are received.
If yes, send notifications to: If the above setting is "Yes", e-mail notifications will be sent to the e-mail address indicated here
Send document with confirmation: Pertaining to the above notification facility, you can send a document from the document library with each notification. (driving directions or what to bring on the first day of classes are examples of how this feature can be used)
Document to send: If the above parameter is set to "Yes", the document indicated here will be send along with each registration confirmation e-mail.
Force Respondents into Group: NeatClubs has the notion of a "Member Category" or "Member Type". This setting controls what group new registrants will be forced into. For example, if a Member Group called "Recreational" exists, we may want to force new registrants to be firced into a category named "Recreational"
Group to Force Respondents into: This setting applies only if the previous field is set to "Yes". Choice will be based on available Member Type Definitions.
Always accept into database automatically: In the System Setup under Registration Behaviours, NeatClubs can be configured to insist that administrators review and approve each login request before users are permitted to login. For most registrations we normally want users to be able to login and self-administer their member profile without administrator involvement so this is normally set to "Yes"
Respondents have visibility to one another: This should normally be set to "No", however in some types of organizations "Yes" makes sense. For example, in the case of a registration event available only to existing members, where members already no one another, it might be desirable to show a member the names of other members who have registered for the same event.