Customizable vault item templates

Custom item types are on our backlog - but in regard to this, perhaps this is just an extension of that function such that you can have a custom ‘Login’ item type with your preferred fields instead of having to manage custom fields + default types as well as custom item types.

Also, for today, we recommend creating a blank item with all the fields you’d like to use and naming it as your template, and leveraging the clone feature to recreate it. I know it doesn’t address filtering, but hopefully it saves keystrokes, clicks, etc. :rocket:

2 Likes

One more thing, in India pretty much everyone has a unique number kind of like the social security number. It’s called Aadhar card. Basically it’s a physical card with the number. It would be great if you could make template for this under the card section or identity. We also have lot of other cards and numbers. The government does have a document vault but I was just wondering if you could include it as well…I think Enpass has a template for this. It’s okay if this is not on your radar. Just wanted to mention this :grinning:

1 Like

I am here too bump up this feature request as well. And I have a much simpler used case that is far more common: many websites require logins that have both a username and an email. It’s arguable that a dedicated email field in this day and age is far more common to a login than a username.

It’s important knowing which email is associated with each login as most websites require email for one purpose or another even if the login is technically just a username and a password. Gold standard password managers like PasswordSafe have fields for each entry by default that make standard the difference between a username and an email address for a login. It is so common that it deserves to be a default custom field in Bitwarden terms but seeing the comments here I can see how different regions and nations would have additional needs for default custom fields for unique, regular reoccurring login fields.

The bigger point here is that good software design uses human-centered design approaches that understand the customer’s perspective. As it stands right now Bitwarden is wasting so much of its customers’ time because there is no option to have a default, reoccurring custom field so its thousands of customers are manually doing this over and over again. It would be really great if this application would be able to catch up to open source software like PasswordSafe that has had a dedicated email field for many years. It would be smarter to add custom fields, with options to make them as defaults in every entry, so that users could customize to their local realities.

Hey @danlatorre I’ve merged your request, as customizable vault item templates are on the roadmap, which would allow you to layout your vault item entries as desired.

1 Like

As a Lean Product Manager myself, I understand good roadmaps are never overly specific about dates, but is this feature upgrade weeks, months, or years away from getting into production? I’m evaluating PW manager options to migrate to and don’t want to go backward from what I currently have (PasswordSafe+iCloud).

Hey @danlatorre the roadmap gets refreshed at the end of each quarter as development becomes more clear, so we’ll have a revised roadmap towards the end of the year with update timelines.

@bw-admin
Recent convert from mSecure to BitWarden and as a Premium user, I need to ask directly, when can we expect the updated roadmap?
Needless to say I need the custom templates feature a lot.
Later edit: it’s available here: Bitwarden Roadmap

I switched from LastPass about a year ago (after about a decade as a LP user) and noticed that all my software licenses, credit cards bank info and other specific note types were all imported as regular secure notes. Not a dealbreaker but it was nice to have all those subtypes neatly organized with their own fields.
Custome templates would allow me to reorganize those items.

1 Like

Just migrated from LastPass after 10 years with them. For the love of god, add this feature. It’s must-have in any modern password manager.

Thanks for your patience everyone, the team is working on this one :+1:

2 Likes

Yes, the best news of the month :smiling_face_with_three_hearts::smiling_face_with_three_hearts: and thanks to everyone, who supported this request in the past!

Migrating from LastPass, same as above. Looking forward to seeing templates and different data types (date being probably the biggest one).

I’d love to be able to customize the existing Identity template and make my own. There is a lot of additional data I need to use often because I manage all my elderly father’s business for him, and I need to provide info like his Birthdate and Driver License Issue and Expiration dates, and while I can add fields for that, they aren’t listed with the other relevant data.

+1
really need this feature

I’ve ended up doing a sort of this as a workaround on my own, so it would be great to have it built in as a feature. Thanks.

Hi just wanted to ask how the team is coming along with adding this feature request? Saw back in Jan an employee posted that the team is working on it. Thanks and is there a place I can sign-up to become a beta tester?

Thanks for checking in, this is in development, you can find information on available beta programs here: Beta Programs - Bitwarden Community Forums

I would love to see the ability to define global custom fields that could then be filtered using a syntax in the search field or new UI elements. The extensability seems like a lot of effort, but I wanted to have posted it. One use case I came across is a phone number custom field or a boolean for phone number usage so that when you change your phone number you can filter for all the accounts you need to switch the number for.

@pascald Welcome to the forum!

It seems that your request may overlap with the following existing Feature Request. Let me know if you agree, in which case I will merge your request with the existing one.

Hi there and thanks for the welcome!

I agree! As long as that would allow us to add another field to the existing „Login“ item type, yes!

I did search, but not thoroughly enough it would seem. :slight_smile: