Additional item types (pre-defined)

[MFKDGAF]

Having pre-defined items types such as Login would be very beneficial. To be honest, all your competitors have them so I do not see why you do not.

Here is my situation:

I have a piece of software that requires me to login to it so I have a Login type entry for it. The software also requires me to create an encryption key. So I add a hidden custom field but in order to generate a password for it, I have to save the item, go to the password generator, copy the password, go back to the vault, edit the item and paste the password.

From a user experience, that is horrible.
I should be able to add an additional password field in my Login item and generate a new password from within it.

[mary-lou]

It looks like it is on the roadmap, but is there an ETA?

We would love to be able to defined our own types / templates or at least have more than the 4 that are currently available.

It is what keeps us from moving to Bitwarden.

[volte (Dale)]

Same. 2025 and the developers can’t figure this out? Doesn’t give me reassurance that the software is built with any reasonable best practices. This is childs play for any developer worth their salt. Pretty wild it hasn’t been implemented yet. I can’t switch from 1Password7 no matter how difficult of an experience they (1Password) is making it for me. I just can’t. I’m working with Enpass now, since they at least support a reasonable number of other types. Would love to throw my allegiance behind BW, and would even pay (despite my obstinance towards paying 1Password), but without table-stakes features, it’s a no-go for me.

[MHunter]

Why? 97K views, 700+ likes and 5 years?
I know it’s nice to try to keep adding the latest features but it’s obvious that when the post read says 39 min this is of high interest.
I’m a developer, Product Manager and business owner, so understand all the competing issues in feature requests, but sometimes basic user experience features add more customer sat. than the ‘new shinney thing’. If the base data structure would need to be changed, what about allowing for the edit of a current card type with adding custom fields but saving it as a “Personal” card type, still using the internal type of say “card”.
Say I want to create a Bank Card, but I need to have Website, login and password. I use the Card Type, add my customer fields to it and save it as a New Card Type of “Card w/login”. This should not be hard as I can already do this, but I have to create the card with custom fields each time I need this card type. Don’t get me wrong fully custom cards would be the best solution, but his would help on the path to this.

[GMichael (Michael)]

I’d love to see more categories available for saved items beyond just passwords and secure notes–similar to the ways LP and 1P offer a variety of categories to organize information: bank accounts, SSNs, memberships, email accounts, medical records, etc. The medical records seems like an intuitive option with the ability to save documents to the vault. As one who have had both LP and 1P accounts, those functional categories were helpful but also added to the graphical organizational aesthetics.

Thanks for the consideration, and if I posted this in the wrong area or there’s already a similar feature request–my apologies. I tried searching through the forum but I’m (admittedly) a forum noob.

[Nail1684]

@xiixexe If you look at the first post of this Feature Request, there is a “staff notice” about them working on it right now.

[Webysther_Sperandio]

A progress but this need to be enabled because is a beta feature.

[Webysther_Sperandio]

6th birthday was so amazing that they decide to go for a 7th birthday!

[Gerardv514]

When was that message posted there?

[grb]

The language in the staff notice at the top of the thread mirrors that of this April, 2022 comment from @gtran:

Additional item types (pre-defined)

Update from the product team: additional item types are in early development, beginning with a significant refactor of how item types are stored in the database while keeping the product backwards-compatible. This will also enable faster creation of new item types. Making progress!

[Gerardv514]

3 years since that notice, @Nail1684 is your post accurate that it’s still a work in progress, or did this stall for some reason?

[Nail1684]

@Gerardv514

3 years since that notice, @Nail1684 is your post accurate that it’s still a work in progress, or did this stall for some reason?

I agree, things could be quicker. And it would be good, to have dates to such staff notices, so that it is more transparent and neither leads to a misinterpretation of the current state nor a “searching adventure” for the timeframe of the “last update”.

In August 2023, there was an update, that at least the previously announced database changes were implemented:

@gtran

(the foundational dB work was completed earlier this year)

And actually, I think that “it’s still a work in progress”: SSH key is a new item type, isn’t it? (only added in the last months)

And this indicates also a new item type for me.

But yeah, obviously it also “stall for some reason”. I guess that is controversial now, but I can see some things, that came along the way and could have changed plans / avenues - like in early 2022 I think no one had passkeys on the radar. (to mention just one thing)

PS: While we are at it - here the complete update from August 2023:

@gtran

The latest roadmap update that has custom item types under research is to provide more transparency on where the team is on it, rather than folks thinking it would be released soon. The team continues to see the need for our users and community, other items in development have taken longer than expected. Although not in development on the roadmap, custom item types remains on the roadmap as it has significant benefits.

Once this item has started development again (the foundational dB work was completed earlier this year), we will keep the community updated once we have an idea of timing. Thank you for your patience and support.

And here the “latest” update from July 2024:

@gtran

Hi all - we updated the format of the roadmap to only show items in development rather than the previous format that would have a column for items in development and items under research because it would give a false sense of timing. Quarters would roll by and items under research wouldn’t get started. We also included a timestamp to ensure we would update the roadmap at a minimum of a monthly cadence.

Additional item types ended up being more of a challenge where maintaining backwards compatibility across devices and different client versions made this a larger effort. This is a similar challenge with vault item labels. The Bitwarden team has also been embarking on a significant UI refresh across all clients, which wasn’t fully represented on the previous roadmap as it was only shown as the web app.

(Thought: maybe, if there are updates like this, they should be linked in the staff notices.)

[winsql]

Hi

Please add an option under New Item for Certificate. This would allow certificates to be added to the vault.

Currently to add backup encryption certificate, I select Login and add the cer and private key file as attachments. It’s a good workaround but conflates logins with certificates.

[Nail1684]

@winsql Welcome to the forum!

I moved your post into this existing feature request to the same topic.