New main email => bulk change username field

I guess this is not a frequent use case but I suggest it anyway :wink:

I’m changing my main email, from [email protected] to [email protected].
Actually my current email is like [email protected] (. is my old custom subaddressing separator) and I want to update it to [email protected].

So I want/have to go through all my stored passwords to go to each website to change my email.

Here’s what I started to do manually:

  1. Search, and for each result…
  2. Edit the item
  3. Update my email [*]
  4. Clean the URL (e.g. /register, /foo/session-id/)
  5. Click the Launch button to open the site
  6. Sign in and update my email on the site
  7. Save the item

[*] I update it in Bitwarden because some sites don’t allow to edit the email in place, some require to type it twice, some don’t trigger the Bitwarden extension update feature. Also because I often change other data while editing the item, so I’ve to save it anyway.

This process also allows me to clean my stored passwords for sites that don’t exist anymore, or accounts I don’t want anymore.

What I would like to have in the Bitwarden Web Vault page:

  • Be able to sort items by last used (or if not available, at least on last updated).
  • Be able to see the URL and open either that URL or its base domain (e.g. instead of, in a new tab.

Ideally… but too much work for such a rare use case? :man_shrugging:

  • Walk through each result: edit item + (save/delete/skip & next).
  • Auto update email with new value (+ have a temporary backup field containing the old value; temporary = not saved in the item).
    As I use subaddressing, moreover with a custom separator, the update function should keep the tag… which would require to allow us to define a custom (JavaScript) function receiving the current email and returning the new value.
  • Have links “base URL” (remove the path) and “base domain” (remove subdomains, and path).

This feature can also be useful in case you want to change all your passwords. Or at least those old ones that were not randomly generated (so we would probably need a searchable field to store that information).