What is described in this idea and successive comments would counteract industry standards and best practices for authentication security. Our team explored options for providing more helpful error messages, but for security reasons, we concluded that we are unable to provide detailed hints when a user enters a legacy username or non-BBID. However, the "Sign In Help/Request Login Instructions" Custom Text/Message will remain active after Blackbaud ID authentication is required so users can view that information for help logging in. In this area, you could prompt users to log in with their email address/BBID.

Brian is right. This error message is not helpful "sign in failed, please try again".

Janet, not to dig this up from the past but this is going to be a significant issue. I don't believe Devin was asking for a way for users attempting to log in in with a legacy ID to be logged in anyway; you're right, that defeats the purpose of BBID. But I just did a trial with a test account and once the BBID conversion is complete, if I try to log in using the legacy ID, I just get a message that says "sign in failed, please try again".

I can foresee an avalanche of support emails asking why users can't log in, and instead of us having to re-type a million times "please log in with your BBID", it would be very helpful if when a user tries to log in using a legacy ID, the login screen displays "you are using a deprecated ID; please log in with your BBID" or something similar. That would provide a level of utility that wouldn't overburden IT staff, and would also continue to encourage BBID adoption.

Our goal is to promote adoption of Blackbaud ID, so we are intentionally promoting a conversion flow so that users won't be confused with two ways to gain access to their account. We will not be making it easier to continue using their old username once they have successfully logged in with their blackbaud ID email.