Why do you need to manually copy the password? If you only have two matching login accounts, then you can easily switch with one is auto-filled, by pressing the Ctrl+Shift+L until you see the username that you want. Alternatively, click the Bitwarden browser extension icon, and then click the account that you want to auto-fill.
By default, auto-fill will start by auto-filling your most recently used account. If you use your personal account more frequently, then this account will be auto-filled by default unless you have just used your GCP account.
Well thatâs the thing - while it sort of learns the default, it doesnât because there is no guarantee of what the first password to be filled would be. There are some sites where this can be difficult, such as Google, where I have quite a few Google accounts in my vault for various reasons and when Google asks me to re-authenticate, often it has your current logged in user account and just asks you to re-verify your password. In that case, I use the shortcut to fill in my credentials but I donât really get any indication as to which password is being filled in which occasionally leads to an incorrect login.
It would be ideal if I could at least choose an âalways firstâ option or even some sort of priority order for the accounts that match. I would just set all of the other Google accounts disable matching but a number of these are shared between others so I donât want to disable the filling of passwords where others may want that matching behavior. Not sure if I am missing some other sort of workarounds but I would prefer a consistent 1st password that gets filled in.
Yep we need this, I have many paypal accounts but one is primary, I would like it to default autofill the primary but allow manual fill on the secondary options. This feels like a crucial feature for users.
First of all, great product, used for a good while now and encourage others to at least try it, whenever Iâm able.
Something that might be helpful to have, is a âdefault user/passâ for a specific website. For example thereâs a few websites that I log on as others (parents, non-tech sister, etc.), but I also have an account on that website too. It would be great to have my own login details the default.
The favourite feature, could possibly be implemented on a per url basis.
Context:
When logging in the first time (or having to re-login) Auto-fillâs âlast used accountâ per page is lost from the cache: loading a page defaults to the top-most account in the search results.
This wastes time because I have multiple accounts for many sites and when I log-in again my most used default is not selected (some other account I rarely use is, instead). There is no way to set a default (including using Favorite functionality).
Solution:
Have a âdefaultâ checkbox per account login that will auto-fill by default. If multiple default accounts are detected on a page, it will just choose one arbitrarily.
Alternatively, a âPriorityâ number field can even be created to do the same thing as above and give a finer control over the auto-fillâŚ
If none of these are done, at least the âlast usedâ account should be saved across sessions per page but this can have security implications if not done right
Scenario: I need to log into a system and I have stored many credentials for different accounts in this system. These could be testing accounts, api credentials, elevated access accounts, etc. There is one account which is my âmainâ login that I would use 95%+ of the time.
Request: Ability to mark a âdefaultâ or âpriorityâ login when multiple match for a given URI. Alternatively re-use the existing Favourite logins feature and use that, whereby if multiple logins exist for a single URI and one of them is a Favourite, it is prioritised over the most recently used option when autofilling.
Alternatives considered: Changing match detection to remove the alt logins works but I would like to keep them, for organisational reasons, but also because when I need to find those rarely-used logins, I can have the page open and click the extension icon, and all matching logins will display so I donât have to go searching.
It is so annoying when forms get autocompleted with accounts I donât use much⌠I d prefer to be able to make a default or choose for the last one used.
Iâd like to add to this that this is quiet a common use case if you are managing some servers. You sometimes have to use an admin account and the switch back to your default account.
I would like to âset a priority for the matchingâ so that the admin account is only used when you manually want to select something and then the auto fill always uses the user account.
Best Case Scenario:
Bitwarden recognizes my âtoniâŚ@gmail.comâ account and automatically uses that password.
Second Best Scenario:
I use Ctrl + Shift + L to log in. I know I can cycle through my passwords for a given site by pressing the shortcut again, but I never know which accountâs password was filled since I have three accounts.
When a password is filled and there are multiple logins on that page, an indicator should show which account that password belongs to. This feature might eliminate the need for setting priorities.
This isnât a solution for power user cases. An example here is for organisation users. In my case there is a website that I use personally, and with work. With my organisation account, I manage 74 different sets of credentials for the same site. Pressting Ctrl/CMD + Shift + L repeatedly is just not a solution, and I regularly have to go and scroll through the list of accounts to find my personal one which is more often than not, the account I wish to use.
The list of accounts shows first in alphabetical order, and as you start to use them they reorder for most recently used items to appear at the top. So you canât even have a solution by naming the entries alphabetically as this becomes inconsistent.
Having some way to favourite/prioritise items rather than it use a hybrid of last used and alphabetical would be extremely helpful. Furthermore, the most recently used functionality frequently resets after a short period of time/computer/browser restarts making the experience very inconsistent.
Thanks for the tip - I just begrudgingly did this. (I do appreciate seeing all accounts that match a URI without searching.)
I have two accounts saved for a website. Even after renaming the entries, and even though the usernames are already in alphabetical order, Bitwarden iOS insists on suggesting the account that alphabetically comes last.
Likely my top annoyance with this absolutely incredible piece of software. Thank you!
This wonât work for everyone, but one thing that helped me is to change the match detection options to be more specific for some logins.
I have a main login for work which I need to use on a number of sites within the same domain, and a handful of extra logins for specific applications. I changed a couple of those extra logins to match the full host name, giving my main login a better chance of being the first entry for other subdomains.
There is a method to the madness. The sort order is by last-used date, with most-recent first, followed in alphabetical order by those that have not been used recently. The idea here is that when one auto-fills the username on one page, and needs to auto-fill the password on the next page, âmost recently usedâ is the one you probably would want.
Sadly the âmost recently usedâ logic doesnât apply when you are using a sandboxed web session, which is common when trying to log into apps using my Google account.
I always end up having to scroll way down to find my normal login.
This advice prompted me to play around with it. After marking the more frequently used account as a favorite and then going in to the less frequently used account and setting the match criteria as âExactâ rather than never or default. This produces a more desired result in my opinion because now when I go to the site it defaults to the more frequently used account set as a favorite and still shows the total # of accounts for that site in the extension icon which also allows you to click to it quickly rather than having to type search for it on the occasions that you do need the less used account. *note that this was only tested with one specific URL with account login fields on main URL home page, results may vary with different URLs. Hope this helps. @WitBarden
I appreciate all the proposed workarounds. But it still doesnât make up for what would seem to be a simple solution to add a flag to make a card the preferred login for a URI. Sure, the user could potentially mark more than one card as preferred, and then youâd be back to the current behavior.
Iâm a scripter, not a programmer, so perhaps I donât understand why this is such a difficult feature to implement that itâs been open for several years.
As many have said already, having a default login is a very common use case and itâs surprising Bitwarden still doesnât support this. Defaulting to the last used login isnât an effective substituteâbesides having issues cross-device or on mobile apps, I find itâs often actively unhelpful. My main accounts generally stay logged in, so Bitwarden inevitably defaults to some side account I only ever select manually.
I appreciate this may be complicated to implement what with URI matching, but being able to set priority would be a huge improvement. Being able to explicitly tell the software what I want is always preferable to it guessing.
