Additional vault item types
Since I'm honestly too lazy to create multiple ideas I'll just post them as one, sonce they all are just different types or options of item types which should definitely be usable in proton pass, apart from log-ins, notes and the three other options:
1. Item types:
• Bank account
○ Bank name
○ IBAN
○ BIC
○ PIN
• Passkeys
• Identity incl.
○ Name
○ Surname
○ Middle name
○ Initial
○ Short name
○ Instagram name
○ Gender
○ Title
○ Birth date
○ Birth place
○ State
○ Company
○ Phone
○ Mobile phone
○ Address
○ Job title
• E-Mail addresses incl. application passwords
• Companies
• Wifi/Router data
• ID Card
• File upload (e.g. for tax certificates)
• Tax Number
• Tax ID
• Driver licence
2. Options for every Login item:
• Groups (should also be pickable/generatable directly when saving a new login)
• Tags (should also be pickable/generatable directly when saving a new login)
• Subdomain on/off switch (should also be pickable/generatable directly when saving a new login)
• Multiple log ins (Usernames and E-Mail) (should also be pickable/generatable directly when saving a new login)
3. Options under every item type:
• Custom fields with individually pickable custom names (Example: Field name: testfield, Value: test)
○ Text
○ URL
○ Date
○ Address
○ One Time Password
○ 2FA Backup
○ PIN
○ Application Password
Custom sections to divide the custom fields
This is now completed, read more: https://proton.me/blog/password-manager-custom-item-management
-
Membership
commented
What is the difference from before?
-
lordgrover
commented
Tried adding driver's licence but dates are backwards/american stylee.
-
Peter M. Holm
commented
With Mobile Phone add IMEI as field.
-
Nebula System
commented
absolutely need this, similar to 1Password, and also the options for custom fields and sections should be under a general drop down of "add more", like 1Password. these are must haves for fully switching over
-
TCS
commented
Fields, structions, classes, hierarchies, object models... and soon you've reinvented C++ (or other/new PL or database implementation), just add typing (as in "types", rather than keyboarding) and behavior (as in "methods") to the thought. Think structure/mechanics/facilities rather than specific data kind groupings and things may become clearer. Whether PP needs some kind of structured data typing facility is TBD. Certainly just blobs of data in a note is paltry, though, IMO.
-
Shane Thompson commented
Please at categories or tags so we can classify passwords within a vault
-
M
commented
Alternatively, instead of Proton providing all those types, one could allow users to create and save their own item types / templates.
Creating a single item from scratch is now possible; saving it (and thus re-using it) unfortunately not (!).
I have posted this idea here:
-
J. C.
commented
The latest update of Proton Pass added 14 new item types, plus fully customisable item creation from scratch.
The status of this idea should probably be advanced to "STARTED" or "COMPLETED", as appropriate.
-
Rasheed Alhaq commented
The identity section is super helpful, but it feels a bit too rigid right now. Not everyone stores the same kind of info—some might need to save things like “Library ID,” “Health Insurance Number,” or other personal details that don’t fit into the default fields.
It would be awesome if we could add or rename fields ourselves. Customizable fields would make the app way more flexible and useful for different people and use cases. -
George Gaál commented
Bank cards + type of payment system (including international and local ones) + expiry date + CVV/CVC
-
George Gaál commented
Regarding Tax ID - it is very dangerous thing, as every country has it's own format for Tax ID, so Tax ID itself without country's name is nothing. Or one will need to implement arbitrary text field for it (as tax id could be number or numbers + letters). The same for passport numbers.
-
Steven
commented
Item types and templates are the biggest issues for me, trying to migrate from Datavault. There surely are some very common ones, like bank account, software activation keys, local user accounts and logins to encrypted volumes...
Notes are a workaround for some of that data, but it would be nicer with dedicated fields in a vault record. Very often there always is a basic "login name" and "password" situation and some extra fields that vary. Maybe the most elegant solution is to let users create their own custom vault record types. -
TCS
commented
Currently, Proton Pass (PP) allows text notes to be associated with vault entries via entry edit. However, while the feature gives the appearance that notes have two parts: a field name and the actual text note. The hint text in the edit box shows "Field name", but then there is no facility to enter separate text that is associated with such a field name, for the "field name" becomes/is the actual note!
It would be GREAT if one could indeed have a separate field name for vault notes, e.g., "Activation code" associated with the text "ASDFJK-QWERTY-POIUYT-ZXCVBN" (for a software program, e.g.). Also, being able to click-to-copy the associated text (ONLY! Not the field name) is the obvious desireable capability desired.
-
Tom Truyen commented
Also SSH Keys would make sense. 1Password has this and it works great.
-
Dave
commented
And add an SSH Agent / CLI around the Keys
-
Reto
commented
One could create their own vault, but in particular the option to create and share Wifi-QR codes would be a helpful new feature!
-
Kaitlyn P. commented
This would be HUGE especially with some older video games/programs need a serial key or subscription authorization.
-
ibrahimahmad17@proton.me
commented
Allow users to store Wi-Fi passwords in the app.
-
LGA
commented
I'd suggest a broader approach : let users add custom fields and. sections to all types of items including notes. Better even, user defined templates.
-
Daniel
commented
Yeah honestly I also have non-Credit card payment options which I'd like to store. Here in germany we have Girocards which allow you to pay but they have different field which makes it impossible to store. I could maybe use a dummy login for my card but when I switched over from 1Password I was able to use the normal card type there. No idea why it's so restrictive