Is it good UX practice to have a site generate secure random passwords for users and send it to their email or is it better to have them enter their own one each time?

  • 5
    As phrased this is a very subjective question. If you could rephrase it then it will make a better question.
    – ChrisF
    Apr 19, 2011 at 22:46
  • Nothing wrong with a subjective question if you can help someone with their problem.
    – Glen Lipka
    Apr 20, 2011 at 18:31

4 Answers 4


It really depends on the context this account is being created. Typically, if it's a forum account for example, I would prefer to set my own password as I have a generic password assigned for that category of sites. In this case, having a password generated would mean that I would need to change it when I log in, which I would most likely forget unless it is required. This adds frustration later on when I decide I want to come back and find that I have to dig up the original email or retrieve my password.

On the other hand, if I were creating a batch users for an organization on Google Apps, having the option to generate passwords would be handy.

  • Thanks for answer, and what if site offers you a pre-generated password that is visible and can be changed at the moment of sign up?
    – Hawkins
    Apr 19, 2011 at 23:15
  • @user4711 -Would the user immediately understand that they could change the suggested password? I personally would be annoyed. Like andrewthong, I have a routine for remembering my passwords. Getting fHBrQQqaAUIB02#j12 is a reason to register or to forget the site, unless its something I need every day. Apr 20, 2011 at 15:45
  • 3
    I'd also say that presenting a password in plain text in the UI is a security issue. Either send them a one-time use token or let them choose when setting up their account. It's inadvisable to show passwords in plain text (or in an email for that matter). Apr 20, 2011 at 18:59
  • +1 @jameswanless I'm not happy when my password is displayed after I register. Usually hints that the password was not hashed. Nov 3, 2011 at 20:42

A pattern that I prefer is to send the user an email with a link to create a password that only works for a short period of time. Whenever I receive a password, I cut and paste it into the password field. If it automatically asks me for a new password then what's the point of having a temporary password? If it doesn't prompt for a password change, then I lost incentive to create a password because I'm logged in already. Then I would have the password in clear text in my email, which is a security hazzard.

Sending the link to reset the password automatically avoids these issues.

  • Thank you Glen. You validated my comment on Benny's post above. Apr 20, 2011 at 18:55

No. Because people will forget it because it will be random and hard to remember. So some of them will change it quickly to something they will remember. If they delete that email, most probably in the future they forget the password and have to use the 'forget password' link and go through the whole process to change it to one they remember easily or retrieve it.

So why not let the user pick their password upfront?


No, never generate a password!

Why? Just because this site in whatever context is (hopefully) going to be an often visited site, and users always want to choose their own passwords. If the user is given a generated password, the user might think there is a chance that it is a poorly built website. Most web users today are used to choosing their own password. And you never EVER send a password over the unsecure smtp- and pop-protocol. It could be read by anyone having the slightest knowledge. There are even free downloadable sniffing tools around to pick up password sent through e-mail.

Second, the site itself is just a very small part of the users total Internet experience having 10+ sites where username/password applies. If all of those sites used a generated password, the user would lose half of the passwords in a month's time, and you would have to deal with forgotten password administration instead of improving content. Keep It Simple Stupid (KISS-methodology) applies.

Even better, use Open ID, such as Google or Facebook or any other to make it even more simple for the user. Like StackExchange sites. Ever found yourself in need to ask for a lost password here? You've got it by now. :)

  • 2
    -1 for saying 'never'. Being absolute doesn't leave room for edge cases and is not a good rule of thumb. There are times when allowing user selected passwords is desirable and times when it's not. Second, a suggestion about single sign-on temporary passwords wasn't even proposed. That would invalidate your 'never' rule but is often the best compromise. The system assigns a temporary token/password that the user must change on first login. Depending on your situation, OpenID may or may not be good. For the higher ed sector, privacy concerns wouldn't allow it. Apr 20, 2011 at 18:54
  • 2
    @jameswanless: I respect and admire the way you give feedback on my answer. It helps me to answer in better way, next time. However we have our different opinions. The suggestion on Open-ID is just to widen the possabilities on the topics, since we're discussing (in some way) security issues here. Apr 20, 2011 at 19:04
  • 1
    UX.se at its best!
    – SuperFluxx
    May 6, 2013 at 16:00
  • 1
    @jameswanless Are you saying that one should never say never? :) Jan 17, 2014 at 14:06

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

Not the answer you're looking for? Browse other questions tagged or ask your own question.