1

There is a functionality in the system for inviting users in bulk. For inviting users, the admin has to provide the email addresses of the users.

Case 1: If an existing email address is entered, the error message shown is

"This email address is already associated with an account."

Case 2: User enters the same email address for 2 or more users, the error message in my mind is:

"Duplicate email address provided."

  • Do these messages provide clarity on what the issue is to the user?
  • Do these messages draw a clear line between the two scenarios or is there room for improvement?
  • Do we also need to specify the next action use can take for correcting the errors (i.e. Enter correct email ID)?
7
  • What are the negative consequences of submitting duplicate emails? Is it important enough to encumber the process with error messages? Jan 6, 2023 at 10:35
  • assuming the messages are necessary, what's wrong with using "This email address is already associated with an account." for both errors? The cause is the same, the result is the same, and the remedy is the same. Jan 6, 2023 at 10:40
  • @bloodyKnuckles Email ID is the unique identifier for each user so when inviting users in bulk, one cannot provide the same email for two users to invite them. And if an action is prohibited for the user, I believe its important to inform him as to why he cannot perform a certain action. Jan 6, 2023 at 11:10
  • @RouxMartin Because when providing the same email address for two users, it might be that the email address provided is not linked with an already existing account. Hence, the second toast message. Jan 6, 2023 at 11:11
  • You seem to be saying that the second message would only occur if a user enters an email address that exists in the database but does not have an account linked - surely that's a technical/data problem and not a UX problem? if that's occurring on a regular basis then something else is broken and the message will not fix that. Jan 6, 2023 at 11:19

0

Browse other questions tagged or ask your own question.