The ability to be able to create our own custom item templates goes back to 2018. I see it in R&D consideration for 1H23, but there is no confirmed roadmap delivery date. This is a big gap in usability compared to competitive products. When can we expect to see this delivered? Thank you.
The ability to set these up server side when selfhosting would also be great.
Is there any update on this? Itâs been in development for a very long time. Iâve been in the SaaS world for many years, and canât see this being that hard to add plus, other apps have this feature already. Rather, you tell us not going to happen vs us; just waiting without any updates.
I actually am hopefull for once, the 6 most viewed topics are either planned or is being researched for the roadmap, where they have existed since 2018. 2 of the 6 are already even complete! Just noticed I can add multiple accounts!
Would be great to have this feature!
I would like to be able to define user defined âCustom Fieldsâ that exists for all the items (login, cards,secure notes,âŚ) in the vauld/Organization Vault, as âEmail addressâ, âPersonal dataâ,âŚ
To add custom fields, we need to define and add to each item the field and value. I ended writing such information in the text Notes but not following any standard field format for all the items in my vault/organization, and then, not useful to make any type of export or filters to search such value.
Iâm not sure if this is the same as what other are asking⌠but as a long time and paid user of Bitwarden i would REALLY like to clean up this interface. On my phone all I want to to is quickly add notes but I have 3/4 of the page with options I dont need. Folder? Favourite?? Master Password??? Iâm trying to JUST add an address to a text box, I dont need all this complication.
Then the box I need to add text to is small scrollable field which means on my phone the keyboard appears and disappears. Itâs very problematic ![]()
I would REALLY like an option to clear all this unusable options and JUST use it for what I need. Itâs even worse needing glasses, having a beer⌠You want to take a quick note from something in real life and I have to fight Bitwarden to get it done.
Bitwarden is great but this BUSY interface is annoying ![]()
Cool, just learned this actually made it to the roadmap (currently under research), thank you Bitwarden Support! ![]()
Iâd like to add/stress: custom item types should also include the ability to define custom values, not just (custom) fields. E.g. for certain logins I use the same regular expression for an URI. Would be cool if Password Manager automatically adds an additional URI with value=MyRegEx and option=RegularExpression whenever I create an additional item of that custom login type.
Keep up the good work!
+1 for this feature but with a slight modification.
Instead of âtemplatesâ I would like to see the options to add all the different field types to a secure note while being able to rearrange the fields anywhere you want along with adding a new type of field called âSectionâ which would be be a space or a line to breakup the fields. The âSectionâ field would be similar to the Section field option in 1Password.
Here is my use case: I store Bitlocker keys in my Bitwarden as a secure note type with text custom fields.
I would like to add the URI of my iDRAC so that when we connect to the iDRACâs web interface, the Bitwarden browser extension will show that we have a save entry for the iDRAC (web interface / website) which would be the Bitlocker keys so that way we donât have to go searching for it.
Another use case: I have some secure notes that I have added a custom text field that has some kind of information in it that is related to a web site. Being able to add a URI field to the secure note, I can then click the open button to go directly to the website instead of having to copy it and paste it in to my web browser. Also the URI field will tell me that I have some kind of information for the website via the browser icon when I visit the web page.
Some examples are:
- Vehicle VIN and vehicle manufactureâs recall website.
- The names of my congress members and the congress members lookup website.
- The names of my states legislators and their websites.
- Serial numbers and URIs to their manuals.
- Part numbers and URIs to their manuals.
- License keys and URIs to download their software
As you can see the current approach that Bitwarden has is not a one size fits all.
Yes, I could create the above as Login types instead of Secure Note type but then when editing I will see the username, password and TOTP fields which I should have to see. Also, depending on your extensions settings, when viewing your vault you will also use the icons for username, password and TOTP which again, I shouldnât have to see.
Example:
So Iâve been running in to this situation more the last few days.
I have a homelab with proxmox and since Iâve been deploying a bunch of LXCs that have web interfaces, Iâve been saving the logins (username, password and URI w/port number).
Some examples are:
- Uptime Kuma
- Sonarr
- Radarr
- Prowlarr
- Heimdall
- Homarr
- Homepage
Since these are local services and not external web services, they donât support any kind of MFA. They only support a username and password.
Because of this I ask again, why am I (we) being forced to have the TOTP field in a login item type when we arenât using the TOTP field (same with notes field).
I think, youâre in the wrong Feature Request thread for this⌠if there came additional item types, Iâm not so sure that we would get e.g. another five variants of âlogin itemsâ, that may or may not meet your request here.
You tackle the ability to customize item types, so you may want to have a look into this other Feature Request: Customizable vault item templates
I have plenty of local service login items, I have never experienced being âforcedâ to enter Totp. In fact that field only shows when adding new or editing, and if itâs not used it does not show on the login view mode.
@MFKDGAF @Gerardv514 I moved your comments into a more suitable feature request topic. The feature proposed in this thread would make it possible to define a new âlocal service loginâ template, which includes username/password/URL, but does not include a TOTP field.
I didnât say I was being forced to enter a TOTP code. I was asking why Iâm being forced to have to TOTP field on a Login item when the login doesnât utilize TOTP.
E.G. Having a card type and having the username and password field on it.
At least for me (Chrome, Windows), âVerification Code (TOTP)â is hidden in view mode unless I enter a âVerification Keyâ while in edit mode. If your experience differs, the inconsistency could be a good candidate for a bug report.
That said, I suspect your request is that the Verification Key not be visible in edit mode.
I donât understand how the Totp field, when not used, is some nuisance. How often do you go into edit item. What about login items that donât have notes/notes not utilized should that not be included in login items too? You donât see these fields during normal usable workflows (meaning view mode).
+1
Sounds like a good idea.
Create basic templates in Notes for multiple items of one type, instead of manually adding the same fields for each entry.
For example:
- Bank Accounts account/routing numbers, site, bank contact info
- Devices make, model, gen, serial number
- Appliances make, model, serial number, support site/phone
- Warranties item, serial, date, warranty number, term/time
@Toni_Hoskin Welcome to the forum!
I moved your post into the existing feature request to the same topic.
While adding a new entry, we add custom fields for some category related entries as per our needs. But its tedious to create again or even clone and moving between 2 entries. Instead if we save that as template, can be readily used while adding new entries.
This should be applicable to existing entries as well, we can change the template by choosing the right one without losing the existing data if they are filled in dedicated fields. For example, earlier if we added custom info in âAdditional Optionsâ field, it should be retained so that we can fill that data into new fields of template by copying from the old field
@sathish You posted in the âAsk the Communityâ category, but as your post already sounded more like a âFeature Requestâ, I moved your post into the existing feature request to the same topic.

