My feedback is similar to a couple of other posts. We have some members who don't have email addresses, so we use a common email address for those members. Also, although rare, we have married couple who share a common email address, but have separate membership accounts. It's a pain, but we have to accommodate our members as is. A warning message during registration would be helpful, but allow a duplicate email address for these exceptions.

This would be a huge problem for us. We have both Corporate and Individual member types. Sometimes a person is both the contact for a corporate membership as well as an Individual member. In this case they would likely use the same email address.

Also, we have executives who assistants who handle all their correspondence. In this case the assistant may be the contact email for a number of different members as well as their own.

I agree with the comments above that suggest requiring unique email by member type. For us, a master account may appropriately have the same email address as a sub-account, but we could require unique email addresses of all sub-accounts. In this scenario, the validation could also apply to updating email after you are a member.

I wouldn't be opposed to having this as a warning rather than a requirement, as some have suggested above.

We ask our individual members to use their email address as their username. It would be very helpful to us to be able to force the username to be the email address for specific member types.

As noted in another post, this has it's pros and cons in our set-up. We have the master account as the company and we assign the "company administrator's" e-mail address to it (the person responsible for billing, roster, and company profile). Then we have the sub-accounts who are the associates under that company. The company administrator ends up with two profiles - the company and their own individual sub-account profile. As such, we will always have profiles with duplicate e-mail addresses. While I'd love to filter profiles with duplicate e-mail addresses, I'd want to do so by master account vs. sub-account level to ensure we don't mix apples with oranges.

We also have an organizational model where the master account and a sub-account will have the same email address so restricting this would not work for us. Could it be something tied to the membership type? A combination of membership type and email would work for us.

I would agree that when a member updates, this should be a check as well. Also, this should apply to staff and members updating/entering new records.I suppose an import could handle the case where we have a generic email to use when it's absolutely necessary. We do use that method, although I'm hoping to get away from it.

I also second the suggestion from R. Dant that new registrations should check to see if they're already in the system (member or non).

I'd much rather have the system recommend the member call us for the occasional scenarios that are flagged with these rules then creating a lot of database maintenance tasks (and member follow up) to correct the issues after they're in the system.

Thanks for allowing us the feedback opportunity!

I agree with a couple of other people who said that a warning prompt when a duplicate email address is recognized would be sufficient, rather than it necessarily blocking the same email address being used.

The most common occurrence for two members using the same email address is couples, which is pretty common among our members (teachers). The other instance is the one J. Haworth mentioned, that when we don't have a valid email address for some reason but have to enter something, we use one of our own domain emails as a placeholder.

We would not want a unique email address to be a primary field for login, however, warning of already used email address is desirable so that members know they already have an account. We have thousands of members in scientific fields and they change email addresses often. They also usually lose control of the email address they registered with us because they changed companies, so they can't recover their account if it's tied to an email address (username is preferable in that instance). We also do not have the staff to manually/administratively recover member accounts, so members need their own way to recover their account with us.

In our case using a single email address per registration is required. We are seen a lot of duplicate records created do to this issue and the work required to keep our database clean is exhausting. Now, is it possible to make the email uniqueness a check option at a setup a page?

I agree with the previous comment by T. Soto. As a YM consultant, many of our clients are frustrated with the ongoing task of managing duplicate records, especially when there are member types available at 0 cost which makes it easy for a member to just create a new account instead of trying to recover the existing one. The feature on events to automatically link non-member registrations to a member account is very helpful, but in the case of a member spelling their name differently, it creates more of a headache to merge profiles.
This has been a hot topic among our clients for awhile. Where does the YM Product team stand on this nowadays?