We have a number of issues with the new strong password feature:
Can’t customize passwords. We normally send out new user e-mails from our CRM. We can no longer do this as we cannot view the password ahead of time.
New user e-mail cannot be customized. It does not include a phone # or logo. Email looks too bland.
Can’t have more than 1 user with the same e-mail address. Since we do not have the ability to log in as a customer, if we are trying to problem solve an issue, we have to create a user id for the account. Customer Service is going to have a problem with this moving forward as you cannot create a new user with the same e-mail address as another use.
Can’t set up users ahead of time as new user e-mail will automatically be sent. Often times with large new accounts we set up a large amount of users in advance and then send out their log-in information on a specific date. This is no longer possible.
Can’t customize e-mail. No logo, no phone #.
Gail,
We are reversing all the changes associated with the secure password, including the email changes. For the redesign, we will work with customers to understand the various scenarios and accommodate them. In some cases there may be compromise in the name of security but we'll discuss those details with customers and try!
We have the same concerns as Gail and Carolyn.
Unique Email - We have several accounts where we have "admin" logins to approve orders when needed and to "see what they are seeing". These typically all have the same admin email address at our company. Unless some sort of "admin" access was granted to approve orders and view the customer's portal view, etc we will need to maintain these "admin" logins. Having to use a unique email for each one is unrealistic.
Generic logins - customers who want to give the masses a login to just look at the site with pricing. Typically we use an internal email for these to help the customer manage these accounts and limit unapproved password changes.
Automatic Email confirmation - we also set up multiple users, approvers, and approval chains without sending the automatic email. Then we can communicate separately when the onboarding process is complete or when the customer tells us they are ready to notify their users and switch over to ordering with us.
100% agree with Carolyn.
We have more to add to your list Gail. Extremely disappointed that this was not planned out better.
Logins with no email address- had to set up multiples when we went from cookies to sessions.
Generic logins - customers who want to give the masses a login to just look at the site with pricing. How do we keep the same password on them? Have no idea who uses them in most cases. No email address on these to prevent resetting the password.
Customer service reps have multiple logins with their email so they can set up recurring orders and in some cases approve for customers who need special attention.
Approver groups – How do we set up an Approver and the users before emails go out? The approver chain won’t be set up. We can’t stop the email now, and we always send out a different email to approvers letting them know what will happen.
Copying of Logins – We copy within an account and make changes to department, approver group, etc. It’s going to be a race now because we don’t want the user logging in before we get the login completely fixed.
Customer who is challenged with password changes – we used to be able to change the email address, reset it and send to ourselves, and set up their password for them.
Solving a problem issue for an account – we typically copy the user’s login and log in to the account to assist. Can’t do this now because of the duplicate email address limitation.
New user email – we added a header and footer last night because it is not very customer friendly. We now will have to send out 2 emails to new users – one as a Welcome and Thank you with their customer service rep information, and then the one from ECInteractive.