Currently it is possible to use one username/password for multiple websites
(by adding multiple URLs to a single login)
I would find it helpful to have the option to have multiple logins for one website without creating three separate entries to my Vault. I have multiple accounts for some websites and so this would be helpful to organize everything
The add new account would look like this
The browser extension would look like this
I solved this “problem” by adding a new item for every log-in like for every family member. If the username is based on the user’s eMail-address it is easy to distinguish between the different logins. I however have to admit that it is much more difficult if for example the username is an account number like an IBAN or anything else you do not know by heart.
I think intermingling multiple accounts in one entry creates all kinds of problems without other UI/UX changes.
Just use the “Clone item” button, should be quick and smooth.
To each their own but I wouldn’t use it this way. It centralizes too much into one entry and if something happens to it then it’s a serious problem. I’ve got dozens of Google accounts and I wouldn’t want them all to be in one entry.
Yes, one simple reason being that there’s a ton of other information that can be stored in an entry (e.g. custom fields) and how would you create a UI that still makes clear which of the 5 accounts a custom field refers to?
Fair enough
Maybe it isn’t such a great idea afterall
I still think this would be a good feature. My use case is I have a few different username/password combos with different permissions for a single SQL database. I have a large note field with notes about tables, and multiple URI aliases for this single database, so it’s a hassle updating those details if I have to have a different copy for each username.
It’s probably a niche feature, but I think a little [+ New username] button like OP’s screenshot would be pretty unobtrusive. Could even have it as an opt-in feature in the settings.
Often websites/applications have multiple credentials and/or I also like the ability to manage multiple user credentials under a single entry. Example with multiple credentials: community forums are typically a separate login from a main website. To me it makes more sense to store both sets of credentials under a single item.
I also share a vault with my wife so we both have access to all the same credentials. When she and I have different sets of credentials for the same website, it doesn’t make sense to me to have to create two different login items to store our credentials. I would like to be able to store two separate usernames and passwords under a single entry.
Currently, I am able to somewhat accomplish this using the “custom fields” function, but the “hidden” custom field option does not allow me to auto-generate a password like I am able to do for the primary password field.
The main benefit of this request is that multiple login entries could be cleaned up and condensed to a single row. This is far easier to search for and organize.
I don’t see how searching will be made easier. For example, if you search for “Bitwarden”, you will immediately see all four items listed (the vault logins and community forum logins for you and for your wife); under your proposal, you would see a single item in the search results (the consolidated item for bitwarden.com). How is this “easier”?
As far as organization of related items, have you considered using nested folders? You could have a “Bitwarden” subfolder that contains all of the Bitwarden-related vault items.
From my point of view, I see your suggestion causing more problems than benefits, and based on the major changes that would be required to the code to implement such a feature, I don’t think it is likely to occur (I have no connection to Bitwarden other than being a user, so this is just an educated guess on my part). Therefore, I hope that the nested folder work-around I have suggested above will help you with keeping your logins organized (which seems to have been the main reason for your request).
I mean, it’s confusing and cluttered to have multiple items show up from the same search result. I personally hate the clutter of having multiple entries, but I must be in the minority on this one. I agree with you that it would potentially be a big change to implement, so it’s likely that it won’t be implemented. At least I can ask to see if others find the clutter as annoying as I do. Oh well. I’ll just start creating multiple entries and deal with it.
+1 for this feature request. I have a set of credentials for testing accounts on my work. And I have rather complicated URL matching rules for all of these credentials. And when I need to change those rules, I don’t want to copy-paste them into each of the vault entries.
Furthermore, it seems this feature will not affect existing user experience in any way because it can be still possible to keep credentials in separate entries.
allow multiple usernames and passwords for a login entering (often needed!) Very often some sites have multiple passwords needed to perform different functions, and the ability to keep memory of past passwords and regenerate them if they expire is essential
In Bitwarden, you would accomplish this by creating a separate vault item for each set of login credentials.
Thank you for the suggestion is what I am already doing but it is precisely not a solution but a workaround
With due respect, the fundamental architecture of Bitwarden is to have a one-to-one correspondence with a different vault item for each distinct set of login credentials. So using Bitwarden as it was intended to be used is the solution.
If there is a valid reason why existing functionality is insufficient, then you will have to describe your use-case in detail and provide some rationale to justify the need for what you’re asking for.
The one example (from my past) I can think of was a shopping site that required user/pass for login and then at checkout time required you to enter a separate “checkout PIN”.
Today’s solution would be to use an auto-fill custom field and control-shift-L at the appropriate time.
This is a super important thing to understand. The vault entry is for the credential (username/password), not the website.
If you have two different credentials they belong in separate vault entries. Beyond just a password, there may also be different TOTP, passkeys, auto-fill custom fields, password histories, etc. associated with them.
I will certainly try this solution and if it doesn’t work I will try to create a screencast of the situation I find myself in in order to illustrate it better.
But I certainly agree with @DenBesten that multiple passwords may be needed on a website, and consequently the current single password structure on some sites may not be sufficient
Is there a guide for this function by any chance ?
Thanks for the tips anyways
Yes, create a custom field for the secondary password. This Document explains how to create them: https://bitwarden.com/help/auto-fill-custom-fields/
What kinds of problems? I don’t see any.
