Anonymous
My feedback
21 results found
-
55 votesAnonymous
supported this idea
·
-
40 votesAnonymous
supported this idea
·
-
589 votesAnonymous
supported this idea
·
-
25 votesAnonymous
supported this idea
·
-
1,231 votesAnonymous
supported this idea
·
-
22 votesAnonymous
supported this idea
·
-
92 votesAnonymous
supported this idea
·
-
178 votesAnonymous
supported this idea
·
-
286 votesAnonymous
supported this idea
·
-
198 votes
An error occurred while saving the comment Anonymous
supported this idea
·
-
514 votes
An error occurred while saving the comment Anonymous
commented
Exactly, this is a must-have for Proton Pass. We look for ability to:
- Detect duplicated entries (automatic suggestions for merging entries)
- Manually merge entries on demand@Proton Please consider users' voices :) Thanks.
Anonymous
supported this idea
·
-
3 votes
An error occurred while saving the comment Anonymous
commented
True, in deed I was told by Proton staff member that ONLY IF you first create the SimpleLogin account, then link to Proton account, all the SimpleLogin domains can be synced to Proton Pass. This is irreversible and must be in done in such way.
So, like you and me, we created the Proton Pass account then link to SimpleLogin using Login with Proton account, we cannot use SimpleLogin domains in Proton Pass or use Proton Pass domains in SimpleLogin. This is a known limitation and sees like the team is not planning to cater this.
What we demand is SIMPLE - but not catered.
Simply allow paid users to use all available domains under both Proton Pass and SimpleLogin, regardless of the way they created their account. e.g., use .passmail.com in SimpleLogin and use .simplelogin.com in Proton Pass. This is a technically feasible and currently developed feature, but not available to customers... Please, Proton, consider taking action to make it available to us.Anonymous
supported this idea
·
-
7 votesAnonymous
shared this idea
·
-
831 votesAnonymous
supported this idea
·
-
135 votesAnonymous
supported this idea
·
An error occurred while saving the comment Anonymous
commented
Hi, your cleanshot screenshot links seem to be expired.
But, I DO AGREE with what you mention. Proton needs a proper NATIVE AUTOFILL for MacOS.
What we want is that, we should be able to select Proton Pass as the source for autofill in settings of MacOS.
Why is this important?
We need native autofill, so that we can simply do a secondary click (or mouse right click) on anywhere,, select autofill and fill from Proton Pass. No need to rely on Chrome or Safari add-on, and we can even autofill in other apps. e.g. when logging in on the Microsoft Word app. -
8 votesAnonymous
shared this idea
·
-
1,822 votes
This is part of the autofill improvement, which is ongoing, this was highlighted in the recent Roadmap: https://proton.me/blog/pass-roadmap-spring-summer-2026
We should have a significant enhancement via iframe coming soon.
An error occurred while saving the comment Anonymous
commented
Same problem here.
For webpages has a two-step signin block that separates the username and password into two pages, there is friction existing.
Some common website that has two page sign in AND CURRENTLY NOT ACCOMMODATED:
- Google Account
- Apple Account
- Microsoft (Personal) AccountProton should look into this and build a data base to handle these types of situation. I would suggest to have an ACTIVELY MANAGED DATABASE OR FEEDBACK POOL that allows users to contribute and report the webpage concerned.
Anonymous
supported this idea
·
-
209 votesAnonymous
supported this idea
·
An error occurred while saving the comment Anonymous
commented
I would break this suggestion into 2 parts:
1. Having categories or tags for items WITHIN a vault. e.g., within personal vault I may want categories like Email Services (Gmail and Outlook) and Mobile Services (Apple and Samsung Accounts)
2. Having sub-folders WITHIN a vault, vaults are usually too broad in context, e.g., Personal, Work, and you may need to further classify credentials into folders. You may need a folder to save credentials for 'Customer Service Agent Accounts' under the Work Vault.
I would say this is really related to the degree of freedom and customisation available - cannot see reasons for not having them. Introducing them will only enrich user experience.
-
483 votesAnonymous
supported this idea
·
-
1,722 votes
An error occurred while saving the comment Anonymous
commented
@Proton Team, could you please at least let us know the status of this idea? Working on it, declined, or what?
An error occurred while saving the comment Anonymous
commented
Yes - absolutely a pain point at this time.
I migrated from Apple iCloud Passwords. Some set of logins, e.g. a Google Account, may have more than 1 URLs for login. When importing, they are separated into different sets of logins.
Please set a feature to automatically DETECT AND ALERT USERS ABOUT SUSPECTED DUPLICATED LOGINS. This is a feature that is present on most of the password managers, e.g. iCloud Passwords, Chrome Passwords, 1Password.
Proton needs this feature to catch up with the market!!! Proton Pass will be in disadvantage without basic features like this!!!
Anonymous
supported this idea
·
Agreed, there is no reason for using Proton Authenticator since all previous TOTP are stored and organised securely in Proton Pass. Proton Authenticator basically just separates a feature from Proton Pass which is unnecessary.
However, conditional on the improvement that all TOTPs are directly synced between Proton Pass and Proton Authenticator (of course will need to have the feature to detect duplicates as well), then users may find it easier to apply a TOTP using Proton Authenticator and that's where it starts to differentiate and become useful.
So, definitely there should be syncing between Proton Authenticator and Proton Pass.