Tag Info

New answers tagged


There are a few things here that would need to be optimized and improved IMO. If verification email has gone out and not confirmed - remove that account or mark it that someone else can claim that account. The worst thing you can do is to lock an email address and don't allow an owner of that email to register. Some websites force the user to reset a ...


Fix the system problem first When someone submits an address, a date should be attached to that entry. If the address is not validated within a given amount of time, the entry should be set free.


If an account has already been created using a pre-existing email (either by error or other situation entirely) you would prompt the user like you've outlined. "There is an account with this email already setup." Then offer a suggestion on next steps to continue the process: Verify the email address you entered is correct. If [email] is yours but you have ...


download bmml source – Wireframes created with Balsamiq Mockups The button should state what will happen when it is pushed, from the perspective of the user. Hopefully this will represent what they are thinking 'I want to activate my account'. Make sure it is extremely obvious upon opening the email, since a high percentage of users will be on ...


It's always a pain to see registered users NOT activating their account. It's an age old problem! And you're right in asking this query. From my practical experience, I would suggest you to: Try sending 'text mails' especially when it comes to account activation/password reset. This is keeping the email delivery and open rate in mind. Avoid only giving ...


Use Option 1 "...to activate..." for consistency This really feels like splitting hairs. I’m right behind you when it comes to fine tuning copy, but this is a scenario where the pressure is off. For a lot of users, account activation is practically automated. The process looks something like: Read alert “We sent you an email. You must…” Go to email and ...


Good UX is to let them log in, and then once they're in inform them of their ban/suspension, and the reason for it (broadly, you may or may not wish to go into more detail than some broad categories that are defined under a ToS)


Denying Login without a ban message has a tendency of making the user try and fix the problem... which can increase the workload on your support staff, and can create confusing activity logs that are hard to tell from an attempt at ban evasion/hacking, in turn making it more difficult to reevaluate the ban at a future point in time.


I think from a UX perspective you need to write in correct English usage. The word Suspend is when you will take something away from someone over a given amount of time. The word Ban or Banish is when a user cannot go to your site ever again or indefinitely. If you plan on putting a timer or time frame around a punishment quit using the wrong word. ...


Make sure the user enters right password before displaying any message. Display a simple message noting why cant he login (here, he/she is banned). Also if possible display the reason and time remaining (if temp ban) if possible. Provide quick links to help, any related page and contact page if the user wants to contact the support regarding the ban.


Alternatively, you can use a "Login Failed" dialog box to tell the user 1) that they can't be logged in, and 2) why they can't be logged in. This might help you keep your code shorter (since you could, say, create a loginFailed method that accepts a "reason" as an argument)


Well, how it's done there, on Stack Exchange? If you're suspended, you still can log in and log out when you wish, though you can't do anything until your suspension is over - and, in most cases, the message in the profile of the banned user provides a reason for them being banned, though you don't get any message when you're logged in, except the rep in ...


Unless you're willing to fully Hellban them, show them the reason they can't log on. A generic error message would just cause them to seek support.


You should always show a message. User needs to have some sort of control, even if it is a simple you are temporarily banned and showing of the timer ( duration of the ban ) I would also suggest adding a button " contact us" where that user can dispute if needed, maybe they feel it was unfair or whatever...basically give them an option to be heard.


From a security perspective, make sure you're only showing messages if the user has provided their password, even if they're banned. I would recommend a ban notifcation (including time), when the user attempts login, show them the reason they were banned and the length of time they were banned for. if there is an appeals process, this would also be the ...

Top 50 recent answers are included