1) The problem → I would like my users to just login using a username and password, not email and password.
2) Why is this important → My website utilizes usernames more than email in the user experience.
3) What's your plan B → Leave it as it is and have users login with email and password.
4) Possible solutions we could build for you → Allow for custom login fields to work with usernames, rather than just email.
8 comments
We are not planning to solve this problem right now. The vast majority of our customers are using emails to authenticate, so we're going to stay focused on emails for now.
Please upvote or comment to receive notifications.
Usernames
It would be amazing to add the ability to signup and log in with a username vs. an email address or have the option to do one or the other. The membership site I’m running primarily works off usernames and not the user's email address. Adding username support within Memberstack would be highly beneficial.
Require a unique input (Username, URL, etc.)
The problem → I need a way to prevent duplicate inputs like usernames.
Why is this important → I can't have members with duplicate inputs.
What's your plan B → To create my own separate database so that I can validate input before the user tries to create an account.
Hello,
I would like to ask if anything has changed in two years and do you currently plan to include this feature in your portfolio. As I wrote in this post - This is an important feature, users take their username as their brand and if this feature does not exist, someone can take the same username and impersonate another user in the comments.
Thank you, Sincerely R. Č.
Hey Radek 👋 We did recently release a new feature which could help. Members will still need to sign up and login with an email, but you can use data tables to collect UNIQUE usernames. And you can require the username when folks are posting. It's going to require some custom dev work to integrate, but it is technically possible now.
https://www.memberstack.com/features/datatables
Any suggestions on what to do when an existing membership base doesn't rely on unique email addresses? The org I'm building for has never enforced unique email addresses for members, and there are some cases where a parent uses their email for themselves and a youth member (because the youth member is too young to have an email).
I've been proposing alternatives with a primary/secondary member model, but the client is extremely wary of this and would just prefer members to log in with their unique member number. Are there any potential workarounds I could look into?
Sam G. Could this help solve your problem? https://www.memberstack.com/scripts/validate-original-values
I don't think it's exactly what you're looking for. I'm assuming the member number you referenced is a pre-defined list which is assigned to parents?
Are students and parents able to create their own accounts, or do you create them on the backend?
Correct, that's not quite what I'm looking for, though I was looking at that script yesterday as a way to potentially prevent folks who are already members from signing up as new again (a common problem this org had in the past).
The client is a sporting organization, so each member (youth and adult) has their own unique membership number, which is assigned by the org. This org never enforced unique emails because they never had to, but now they want to migrate to a more modern system where members can log in to manage their membership.
If a youth member is signed up by their parent who is not also a member (because they don't participate in the sport), there's no issue because there's only one account being created.
The issue is that we have some youth members whose parents are also participants, so they are both members with unique member numbers, but sharing the same email address.
I'll be creating accounts on the backend for existing members, so I do need to find a way to deal with over 200 members who do not have a unique email address. Then going forward, we will still have instances where a parent wants to sign their child up under the same email but can't. And just telling them to use another email address is not ideal.
My current plan is to use Data Tables and create a whole flow and model around "Secondary Members" that are managed under a "Primary Member" account, but so far, the client sees this as overly complicated and would just prefer members to be able to sign in with a unique member number so they can still share emails.
Please sign in to leave a comment.