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.
+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.
What kinds of problems? I don’t see any.
Custom fields are properties of the vault’s entry (not the username/password)
thus there is no problem here when having more than one username/password for the entry.
However custom fields can link to other fields including username/password and in this case username and password should be treated specially and the value used in this case should be the one selected by user from the list of all usernames for this entry during autofill. In other words Username and Password below should be treated like an alias to the username and password used for autofill and not literally which would mean the first username and the first password (in case there is more than one).
TOTP 1
TOTP 2
Password History 1
Password History 2
What if the custom field is “account number”? How would one arrange for different account numbers per password?
What does the auto-fill overlay look like when there are two usernames?
When auto filling with ctl-shift-L twice, does it go to the next vault entry or the next username? And then, does it reorder the usernames so that the most-recently-used is first, so that a ctl-shift-L on the password field selects the corresponding one?
If one is a personal account and the other a shared admin account, how would sharing/access controls be managed per password?
Bottom line is that the Bitwarden design is one vault entry per account, not one vault entry per website. This is deeply engrained in its design. Changing that would not be easy, so the win would need to be big.
I don’t think anybody in this thread has expressed clearly why such a feature would be necessary. If you would like to impose additional organization onto your vault data, you could create a folder for each website, and store the different accounts for that website inside the folder.
