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
-
DW commented
This is precisely why I'm sticking with iCloud's aliases for now. Creating a ton of duplicate entries for aliases clutters my vault and is extremely annoying to have to filter each and every time. Put aliases in a separate area under settings if they're going to be managed separately.
-
CT commented
Tossing in my vote to have aliases somehow separated from logins. I like having them managed in Pass, because I'm usually creating an alias and login at the same time. And I agree that merging them with the login wouldn't work well because you may want to use the same alias for multiple logins. But as a default I'd prefer to see all categories EXCEPT aliases displayed.
I would suggest a totally separate area for them, so that we're either viewing aliases or all other items. I think most people are probably used to seeing logins stored together with saved cards, etc. (which can be filtered if desired), but aliases feel like a whole other thing that could be a separate tab altogether and never mixed. There could also be a way to link the aliases to whatever logins they're used for, to make it easy to move back and forth between those entries.
-
The Wonderful Tartiflette commented
oh yes absolutely, I don't understand why that's not a feature already!
Like, if I use the ABC service that has a web version AND a mobile app, Proton won't understand that the credentials I enter in the "ABC Mobile App" are the same as the ABC website, and will always display those as being different in Proton Pass -
RH commented
For me, managing email aliases through ProtonPass is a step in the wrong direction. An email alias is just that, an alias for an EMAIL address, and as such I should be able to manage aliases directly through ProtonMail instead of having to open another seperate app. For the most past I create email aliases for online shopping, subscriptions to newsletters and other events where I don't want to share my real email address and expose it to spam. IF I sign up to a service that I want to be able to sign in to in the future using an email alias, well I'll do just that and I'll then store that email alias together with a password, URL and any other notes in ProtonPass, but don't force me to use ProtonPass for managing email aliases when the majority of my aliases have nothing to do with signing in to accounts.
-
Phillip commented
I agree. Or even create a separate space entirely in the UI for them. I practice digital minimalism and the aliases make it look like I have way more logins than I actually do lol.
-
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.