Hi all,
Is there a way to delete all items in Bitwarden vault ???
I want to start over, but I don’t want a new account.
Any suggestions?
Best regards
Jan
Hi all,
Is there a way to delete all items in Bitwarden vault ???
I want to start over, but I don’t want a new account.
Any suggestions?
Best regards
Jan
Yes, you can purge your vault from the ‘My Account’ page in the web vault.
Thanks a lot.
What about selected items? I have a huge number of duplicate logins for the same domain. Can I bulk delete selected items?
@richards1052
Log in to the web vault, use the check boxes to select items, then open the kebab menu and select “Delete selected”:
Sorry to reply to a solved question. I have a related question.
When I tried to delete all items and clicked the checkbox next to “All” above the list, it selected only 500 items.
Can I select all items at once? Or do I have to delete 500 items at a time and run multiple times? The same problem exists when moving many items to a folder at once.
If you truly want to delete all items in your vault, you can go to your Account Settings (by clicking on your profile avatar in the top right corner), and activate the Purge Vault function.
@grb Thank you. I’ll do that when I need to delete all items in the vault.
Probably the question should have gone in a separate topic. So there is no way to select more than 500 items at once? I may want to move bunch of items to a different folder for example.
My vault doesn’t have more than 500 items, so I can’t check this for you. But from your description, it seems that the vault view only lists 500 items per page, and that “Select All” only selects the items on the current page?
If so, I would suggest that you make a Feature Request asking for an option to select more than 500 items at once.
If the above is not what is happening (e.g., if all vault items are displayed, but “select all” checks the boxes for only the first 500 items shown), then the behavior may be classified as a bug, and should be reported on GitHub.
There’s no pagination and I can scroll down to the end of the list (containing >2000 items), so it seems like all the items are shown. But it may be showing items as I scroll using JavaScript for efficiency and only 500 items may exist in the page when I am at the top of the list (so that I can click “All” checkbox).
I am not sure but this may be the expected behavior. Actually I can repeat 5 times for deleting/moving all my items, which is not that burden. But I would say the label “All” for the top checkbox may be confusing.
Personally, I would consider that a bug (i.e., unexpected behavior). “All” should mean “all”. At a minimum, there should be some warning message if there are more than 500 items in the list. Please consider filing a bug report.
@grb Thank you. I agree that this should be considered as a bug. And I now went to GitHub and found the issue was already reported.
I also found this.
Interesting that it is intentional. I still feel that they should implement a warning message when the selection has been truncated at 500.
Gmail also selects only the first 100 conversations by clicking the top checkbox (the number of conversations per page is configurable and list is paginated in Gmail though). But it shows a warning like “All 100 conversations on this page are selected.” and also provides a link to actually select all conversations in the mailbox.
A simliar UI may be ideal but just showing a warning as you suggest may be probably sufficient for Bitwarden.
When a list is paginated, it is not uncommon UI practice for “Select All” to only select all items on the current page. However, this is not what is happening in Bitwarden, so the current behavior is unexpected.
Well, I don’t mean selecting only 500 in Bitwarden is acceptable since Gmail does the similar. Rather I pointed out even the paginated UI like Gmail, they choose to show such warning to avoid confusion. Silently selecting only a part of the listed items by checking a checkbox labeled “All” is definitely a confusing behavior. I would say it’s a design flaw if it is intentional. The issue is still in Open status so I hope it will be fixed at some point.