Limit event registrations to one per member/email
When registering for an event, someone can register as many times as they want using the same email (so long as they don't exceed any event registration limits). This was initially set up so that guest registrations could be submitted if someone didn't have the email for their guests, but this is in the process of being completely implemented with Multiple registrations for an event
Some people have asked for the ability to limit the number of registrations that can be submitted under one email. This way if someone entered an email which was already used for a registration, the user would be notified and unable to complete the registration until a unique email had been entered.
This would be an optional feature which you could turn on for the main registration, the guest registration or both.
Released in v5.5 – see http://help.wildapricot.com/display/DOC/Release+5.5
I've wrote you an email to address Mark has given me.
This option is customizable both on event and on registration type level, you can turn it on/off depending on your needs.
Meanwhile, could you please elaborate how you use events to handle CPD (CPD stands for Continuing professional development, doesn't it)? Actually, we have a dedicated thread here: http://forums.wildapricot.com/forums/308932-wishlist/suggestions/8825617-tracking-continuing-education-points-ceu-cec-cp I would appreciate if you post your comment there so we not lose it when start working on it.
Amon Houston commented
Is it possible to give us the option to turn this off? Like I said further up in this thread, we are using this 'bug' as a way to handle CPD log details as Wild Apricot has no current CPD log feature.
And using an external service to handle that stuff seems like an unreasonable ask.
The other thread is about a different issue altogether (and frankly is all over the place in terms of problems/suggestions). It looks like I'm not If you have 10 minutes, give me a call. At this point, I'm not even confident that I am sufficiently communicating the issue I have... Mark Faccia knows how to reach me.
The issue is not that simple as it seems at the first glance - it is tightly connected with updating contact data from registration form and vice versa. Most appropriate thread for discussing and tracking progress it is probably this one http://forums.wildapricot.com/forums/308932-wishlist/suggestions/8826433-member-or-contact-profile-differs-from-event-regis - this limit will be most likely addressed there.
Oleg, can you add my suggestions to your backlog and give me some idea where it sits on your team's backlog (to set expectations)?
There were two main scenarios that we solve:
1. Register using member's email to get discount for event (if there is one)
2. Avoid duplicate registrations (e.g. when user just forgot that he has already registered or just wants to update registration form).
Your suggestion would be very helpful for first scenario, indeed. But we missed it during our analysis and issue is in development already. We cannot change scope on the fly, w/o proper analysis.
Thanks for the (very disappointing) reply Oleg. I really don't understand what is being addressed by your changes if you're not doing this, as it is central to this entire thread... What scenario are you addressing if you allow a member to register someone else with their account?
Dalek, thanks for your feedback.
For now we didn't consider the scenario you suggested (registering yourself only), but we may implement it later.
Amon Houston commented
I'd actually like to keep this in Until a proper CPD log system has been implemented. Right now we use this so members can sign up to the CPD Log - 2015 event as many times as they want to fill out this information. Since there is no other suitable system otherwise.
Here is an example with read-only fields:
Example of read-only fields during event registration:
Oleg, it's great to see that this is being addressed! Thank you for your customer focus!!
I reviewed the deck from your post above and have a question about how this will work. Specifically, while I need to have registrations limited to one per contact, I also need the registration to be restricted to that contact. Namely, I don't want the ability of a contact to sign up someone else.
Today, the first and last name fields of event registration are populated with the names of the contact who is signed in, but the fields are not read-only and so can be changed. If these fields were made read-only with this change, or we add another option to limit this such as shown below:
I am strongly in favor of having the option to limit registrations to one per email address. We also have several memberships where husband & wife share the same email address. Would it be possible to have the bundle members listed with the option for the member to check if they want to also register their bundle members? IMHO, this would prevent duplicate registrations and also speed up the registration process for the user. They would no longer have to go back & go thru the entire registration process again for the second member.
We are planning to add multiple registration limits to one of the future releases. See presentation below for details:
This feature will be addressed in one of the upcoming releases - please track current progress in our Roadmap http://help.wildapricot.com/display/DOC/Product+roadmap .
Meanwhile, please comment on what you think on suggested solution
Add my vote on being able to restrict the number of registrations per email. When a limited seating event closes out, I have to check & see if there are duplicate registrations. (there is normally at least 1 or 2). I have to manually remove the duplicates so those seats don't go unfilled. I do not know how many members may have tried to register & found it closed out before I could remove the duplicates.
Please don't take away the ability to allow multiple registrations per email address. If you allow the restriction of one registration per email address, please make it an option (even the default) but not mandatory. Thank you!
My team is working on analysis and design of this requests right now.
Absolutely yes to this one as an option.
I have paid members who submit twice with their login details - once for themselves and then for "friend" who has not paid.
Another vote for a way to prevent duplicate registrations. Although we do have a few husband-wife members who share an email address; this would be a way to encourage them to go ahead & get a second email address.
PLEASE limit them. The guest registration resolves this issue.