Merge passwords and aliases
It's nice to have Password and Aliases but the main goal of aliases is to replace the email to use it for a login, so with a password. Having aliases and passwords separated forces us to have duplicated entries for one login. It kind of double the entries for nothing and would be better to manage all this in one entry
-
Genevieve commented
13Jan2025: I opened the (Android) app so I could write a more detailed comment in agreement, and found that you can now view by type: all, login, alias, note, card, identity. I had overlooked this and was using "all" and getting frustrating when two entries would show up (alias and login) in a search, because invariably I would then click on the wrong one. Anyway, I will be using the "login" view from now on.
-
Brooks commented
Came here to say this. Alternatively, aliases could be removed from Pass altogether and managed within, ya know, the email app, instead of the password app. Crazy idea, I know.
-
Anonymous commented
You can't merge them because you then can't use the same alias for more than a single password entry.
The proper feature would be to create a dashboard specifically for alias management... Instead of viewing from the individual password node, view from the alias node down to the children logins.
But I sort of agree the mental model for most of us is that these are two separate things.
-
marc commented
Yeah, I accidentally sync'd all my aliases from my Simplelogin into Pass. I've put them into a separate vault called "Aliases" but when viewing "All vaults" it looks so messy. They really need like a separate panel/console for alias management instead of having all the aliases as items in the vault.
-
Brancu Alexandru commented
This would be super useful, having multiple passwords for the same alias.
-
curmudgeony tom commented
When creating a login manually, and entering an existing alias as the email, the UI changes from "Email" to "Email (alias)" because it recognizes this email as an actual alias. Similarly, when deleting an alias that is used in a login, there is a warning that it is used in another login. So Proton Pass already knows that this login is connected with the alias! Then can the login entry also have a toggle to enable or disable that alias? Or can the login at least have a link to the alias entry in Proton Pass?
When creating a new login and selecting to create a new alias during the creation process, these entries should be linked and represented as a single Login.
-
proton_evol commented
very good idea !
-
Jude Gonsalves commented
Or better yet link aliases to password credentials
-
Wheeljack commented
Maybe have the aliases in a separate part of the UI, but when you create a login that links to an alias, then on the Proton Pass card for that login there should be something that shows the corresponding alias, along with a link to go open it and see the attached contacts etc from Simplelogin. Then a nice disable button next to the alias name that clearly indicates is alias is live or not. No longer need to put things in the bin :)
-
Anonymous commented
Aliases need to be creted separely because they need to be managed (you need to be able to disable them if you start receiving spam, for example, and you might need to create a reverse alias sometimes if you need to send an email from that alias).
However I agree with you. I hate that whenever I create a login with an alias, two separate things are created and mixed up with the password manager.
Also, aliases can't be managed into Pass, you need to go to Simplelogin to do that. So why is the alias entry being even showed in Pass, if it can't be managed within Pass?
A potential solution would be a dedicated area in Pass for the aliases, with deeper integration and pretty much same functionality that Simplelogin - meaning having everything integrated in Pass.