I would like to vote for this!

I absolutely agree with limiting registrations to one per email. This is now causing us havoc to manually have to check on duplicates. Guest registration should work just fine if a member wants to sign up someone else.

In the old version we got a message saying the member had already signed up. How about just going back to that and disallowing dupes. After all, what's the guest registration for if not for allowing the member to sign up and be responsible for anyone wanting to register under their email address.

This is something that should be corrected in the short term and not wait for another full version.

I'd prefer if our members were not able to register twice for the same event. We don't allow guest registrations, and there's no reason for someone to register twice.

A few members have registered for our annual conference, then realized they hadn't paid yet, so went through and registered again, creating a duplicate. Often one registration will get paid and leave another unpaid, which then has to be manually cancelled.

We definitely need this. Maybe our members are just dumber than others but they don't seem to read the notice warning them that they have already registered for the event.

Thanks!
--COFFEY

Thanks for sharing, we will take this into account.

We have many (800 or so) events every year. Most are free, but for the ones that are paid events, we too have separate pricing tiers for members versus non-members.

We really need to prohibit non-logged-in users from being able to register with members-only registration types. It undermines the member benefit. If a non-member knows the email address of a member, they can simply spoof that user and get the discounted rate during event registration.

Putting the onus on us to check for duplicate emails in registration exports is not realistic. We are a volunteer-run organization.

We have just switched from Constant Contact to WA for events. On CC, we required that people registered their spouses as guests. However, we limited the number of guests they could register (this functionality is in CC). We'd love to see this functionality in WA too.

Some of our events are very small and we don't want one member claiming all the spaces by registering lots of guests.

Thank you for comment.

Our organization has the primarily events where we do want to limit registrations to one per member. We have found the ability to turn on guest registrations helpful for a few events, so it is great that this is an option. I agree with the thread above that the guest option does appear to satisfy most multiple registration needs.

We were quite surprised to find out that a member could register a second time and consider this quite problematic. We are fortunate in that we don't have husband and wife members sharing email addresses, but I agree the guest registration would handle that circumstance.

Regarding the ability to edit a registration, we generally do NOT want the member to be able to edit their registration since we have found a need to add some items to the Registration form that are for Administrative Use Only and we would not want the member to be able to modify these.

My experience as a system engineer is that making things configurable is best to allow people flexibility. The trick is not having so many configurable parameters that users are overwhelmed. One possibility to consider is having the ability to configure WHICH fields can be edited by the registrant. This would be something link the 3 level control for visibility of member attributes. Perhaps some fields could be edited, some could not, and others would be for administrative use only.

I do hope we seem the ability to limit the number of registrations per member/email soon.

A Rimpo - Baltimore Watercolor Society

Hi Evgeny

I don't envy system designers - I thought the answer I would give would be very straightforward but thinking it through, there are many complications to think about!

If the wife and husband share the same email address and both are attending, they should be able to use the guest registration facility. However, the 'guest' should be allowed to use the same email address as the 'host'. This would mean that the validation should only apply at the 'host' registration level. In fact it might be helpful to have the email address of the guest filled in with the host's email address as a default that can be over-ridden (and maybe even all contact details?)

There is one problem to think about given that it is not, I believe, possible for a Member to amend an existing registration. If a Member registers and then tries to enter another registration, presumably the error message will say something to the effect of 'please use different email address or enter this registration as a multiple registration for the existing one'. How will the person do this? It might be necessary to allow someone who has already registered to be able subsequently to add 'guest' registrations, even if they are not permitted to amend the existing registration in any other respect (see also my last point below)

Another question: Should the current facility be known as 'Guest' registration or 'Multiple' registration, because it might not always, as in the wife husband case, be a 'guest'? I would support 'Multiple/guest registrations' (confusingly, the current field label is 'Mutiple registrations' and the only option currently for 'Multiple registrations' is 'Allow guest registrations')

I am generally in favour of new requirements or validation being controllable because one never really knows how people use the system. In this case I would be in favour of a system-wide setting that allowed the organization to prevent the same email address being used to register for an event more than once. This would allow those that are happy with the current set up to not set the validation and carry on as before.

I have another related point. For our Members, the cause of multiple registrations is often because the person registering has not filled in one of the fields on the registration form, so submits another registration with the same email address and the empty field completed. Having the ability to prevent multiple event registrations would get over the problem of such duplicate registrations but might cause frustration and extra work because at present there is no way for the person to amend an existing registration even if the amendment is just additional information (e.g. car license plate). I do not fully understand the reason for not allowing Members to change registration data for existing registrations (maybe this could be another system-wide option?)

I agree but what about scenarios when a wife and husband share same email?

Another question: if we go this way, do we

1) just disable same email registration completely or

2) make this as a setting in the system or even specific event (i.e. disable event registrations with the same email)

?

Now that the multiple/guest registration has been implemented, I no longer see the need for allowing multiple registrations with the same member/email and strongly support the limiting of one event registration to one member/email as a basic validation check. Better still if it is controllable as suggested in this thread and deals with abandoned status (my impression is that the system now handles this much better with the latest release)

If an event has two identical registrations, I have no way of knowing (other than contacting the person concerned) if the second registration is a mistake or is for another person attending the event.

The current event registration screen is also confusing in a number of respects and, in my view needs tidying up: Events that do not have guest registration permitted show the following: 'Multiple registrations Not allowed'. My immediate interpretation of this was that it would prevent multiple registrations for each member/email - not so. Should it not read 'Guest registrations Not allowed'? When you click on the Edit button, the screen specifies 'Allow guest registrations' as opposed to 'Allow multiple registrations'.
Note: This is how I set up the capability for a Member to register another person (e.g. spouse for event that is eligible for guest registration). I do not therefore see the need for allowing multiple registrations with the same member/email

Does anyone feel that multiple registrations per member/email are still necessary even though the guest registration facility has now been implemented?

My only concern with this is that it doesn't block those who are stuck in Probably Abandoned status for an event. Many times these people can't figure out how to fix their original registration and just register again.

I suspect that it can be built so that they would still be allowed to re-register this way, since in that status, they are not really "registered" for the event yet.

We really need the feature of one registration per member email. We have two prices for our events, member and non-member. We often have members signing up their employees (employees we consider non members) at the discounted member rate.