Multiple Logins
Kellie Mecham

Q: Our web-based application currently requires two logins to use: one for the application and one for each module under the application. I’m having trouble convincing others on the team that we should just have one login. What do you think?

Having multiple logins impacts two key usability heuristics. It is a barrier to efficiency, creating two steps where there should be one, and it may cause user confusion by making the system status less obvious (“Am I logged in or not?”). Ideally, re-architect the system so that users only have one login. Alternatively, carefully communicate system status to the user to minimize confusion.