Proton Pass & Authenticator
438 results found
-
Extend custom fields to include existing field types
Currently, the available custom field types are quite limited (text, TOTP, secret, date).
I would like to see Proton extend the range of custom fields to include field types that are already supported elsewhere in entries, such as:
• Website / URL
• Password (which seems to be treated differently from a generic “secret” field)This would make custom fields more consistent, flexible, and aligned with how Proton already handles structured data. It would also allow users to better adapt entries to their specific needs without losing the benefits of type-specific handling (e.g. clickable links for websites, password-specific features like…
11 votes -
Request ESET support
Add import for password protected ESET json files in password manager, Import
7 votes -
Backup / Restore tool for aliases
I tried the backup / restore tool with gpg, zip and csv formats. It works well BUT aliases cannot be imported. They are excluded.
What's the point of having them in the export file if we cannot import them?
Thank you.4 votes -
Mac toolbar app (drop-down)
Currently when pressing the Proton Pass icon in the Mac toolbar it gives you two options: 'Open Proton Pass' and 'Quit'. That is so useless. Launching the app via spotlight search is faster. In browsers you have a nice app that opens in a sort of fold-out/drop-down way. It quickly let's you access it without actually opening the entire app. We need this for the Mac-native app as well.
3 votes -
please insert safeincloud at please insert safeincloud at https://www.safe-in-cloud.com/en/
please insert safeincloud at https://www.safe-in-cloud.com/en/
8 votes -
add auto lock after closing the browser
add option to request pin code only after the browser closes
3 votes -
Generate random Prefix for alias
When creating a new alias, add the option for generating a random prefix with two random words.Example: sheetspray
12 votes -
Proton pass - separate aliases into their own folder by default, separate from logins
On purging my logins/passwords I accidentally also deleted all my aliases, as they're all thrown into the same default folder. They should be in a separate folder by default for clarity that deleting one is deleting the alias itself, not just a saved login/password.
4 votes -
Authenticator app encrypted export
Allow user to set password to create encrypted export of the MFA codes. This feature is in many other apps, and prevents relying on cloud platforms (e.g. iCloud, Proton itself) to create & restore backups.
12 votes -
Authenticator app PIN code
Biometrics are not as secure as e.g. 6-digit PIN code. Other apps like 2FAS have this feature.
11 votes -
3 votes
-
Proton Pass Browser Extension: 2FA autofill/button relocation
This idea applies to the desktop Proton Pass extension (specifically, Firefox for me)
Current flow for login to a site: When entering username and password, the autofill prompt is directly below the input field. For 2FA autofill, it moves to being below the Proton Pass Extension icon in the toolbar.
Proposal: Either have 2FA autofill, /or/ relocate the autofill prompt to be in the same position as the username and password prompts.
As a layperson, I think of the username, password and TOTP to all be fields within an entry in Proton Pass, so I can't think of an architectural…
4 votes -
Distinguish "Vulnerable" passwords from "Weak" passwords in Pass Monitor
Currently the Pass Monitor lists all logins with passwords considered "Vulnerable" and "Weak" together in a long list with no apparent order. Combined with the observation that Proton Pass is fairly aggressive and inconsistent with what is considered "weak", the user will find it very difficult to prioritize for the most vulnerable passwords first.
Login entries with "Vulnerable" passwords should be focused and prioritized, grouped together at the top under a clearly marked "Vulnerable" category, and the others grouped below under a "Weak" category.
10 votes -
Set default domain per vault
Instead of selecting a blanket default domain, tweak it to make it per vault. Hence, if I'm in a vault, the default domain is this vault's default domain. That way, when I switch vaults, I don't have to select a different domain.
3 votes -
Duplicate newly generated alias address to "confirm e-mail" field instead of generating another alias
The current Proton Chrome extension auto fill will input a new alias address in the "e-mail" field (e.g. ra.backboard536@passmail.net), but in the next "confirm e-mail" field the extension suggests to input yet another newly generated alias (e.g. ra.reverence973@passmail.net) when it should obviously just duplicate the one that was just generated (ra.backboard536@passmail.net)
3 votes -
ProtonPass Alias
Composing a new e-mail alias is not straightforward, You cannot add the alias directly to From. You have to create a reverse-alias and add a contact for the recipient. This hides the real email address.
After creating an alias email; the alias should be available in the From drop down list, to use directly.
8 votes -
Allow Labels and VAULTS
I have protone duo, and I want to share all passwords with my wife. Right now i used the only option you provide to create a shared Vault. This however removes them from all of my VAULTS which i used to organize them. I have so many passwords that I need labels for them
5 votes -
Autofill intelligence and reliability
The biggest problem that keeps cropping up in user reviews is the unreliability of the autofill feature. Proton Pass often fails to recognize login fields correctly, fills in fields incorrectly, or logs out unexpectedly. Proton needs to make significant improvements in this area. Competitors such as 1Password and Dashlane have developed significantly more sophisticated systems that can easily handle complex forms, multi-step login processes, and unconventional websites. Proton Pass should use machine learning to learn from failed autofill attempts and continuously improve its recognition rate. A fallback mechanism that automatically tries alternative filling methods when problems arise, rather than simply…
4 votes -
Proton aliases to DUO partner
I would like to suggest an enhancement to the mail‑alias forwarding functionality.
Current limitation: At present, aliases can only be forwarded to the primary Proton address associated with the account. This works well for personal use, but it restricts the flexibility that DUO users expect.
Requested feature: Allow users to forward alias messages not only to their own Proton address but also to the email address of their DUO partner.
6 votes -
Add cloaked to your list of imports
Your list of password imports does not include Cloaked.
3 votes
- Don't see your idea?