Sean Sands
My feedback
16 results found
-
1 voteSean Sands
shared this idea
·
-
2 votesSean Sands
shared this idea
·
-
1 voteSean Sands
shared this idea
·
-
2 votesSean Sands
shared this idea
·
-
2 votesSean Sands
shared this idea
·
-
15 votesSean Sands
supported this idea
·
-
639 votes
An error occurred while saving the comment Sean Sands
supported this idea
·
-
165 votesSean Sands
supported this idea
·
An error occurred while saving the comment Sean Sands
commented
I would also say, allow for merging. When merging, any fields that overlap, create a field that says "{field name} {number of added duplicate}"
-
9 votesSean Sands
supported this idea
·
-
142 votesSean Sands
supported this idea
·
-
3 votesSean Sands
supported this idea
·
-
19 votes
An error occurred while saving the comment Sean Sands
commented
Also, allow me to drag and drop any multi-selected entries in a different vault.
Sean Sands
supported this idea
·
-
349 votesSean Sands
supported this idea
·
-
706 votes
Subscribers now have access to offline view with the introduction of the Proton Pass desktop app for Windows:
For more information, including what's coming next, check out: https://proton.me/blog/proton-pass-windows-app
Sean Sands
supported this idea
·
-
1,044 votesSean Sands
supported this idea
·
-
537 votesSean Sands
supported this idea
·
Custom fields are helpful, but there is a lot of commonality in various fields that should be supplied as part of a standard (or use a standard if one exists; I am not versed in this). Tangential to this, we should have a way to flag a field as sensitive, and some existing premade fields that exist today, like SSN, should be hidden like passwords by default. Adding a way to modify existing fields (and custom fields) would also be helpful.