Option to ignore folders/logins/tag for reporting purposes

I have a lot of IOT devices I use and build, plus cameras, etc. all around my home. They are all internal on an IOT network behind a firewall. I’m in the process of moving my LastPass account to bitwarden. Part of this migration is to change all my LastPass passwords due to the previous security breaches. In total I have over 900 passwords. to go through.

I have all my IOT stuff in an IOT folder and not concerned about those passwords but I am concerned about the remaining. When I run the Duplicate Password, Weak Password, and Exposed Password reports, those IOT devices are showing up and I wish they wouldn’t. To make things worse, the names of these devices are their IP addresses 192.168.x.y so I’m constantly scrolling down to get to the real passwords.

I’ve tried adding a custom Boolean tag but I have to add this tag to every login which is much more work than placing the login into a folder.

It would be a blessing to be able to ignore these passwords for reporting. I still want to keep track of them and that’s why they are there. Any suggestions?

1 Like

@4square Welcome to the forum!

One possible work-around is to create a second Bitwarden account, and import only your non-IOT vault items. This would be a temporary solution just to be able to run reports, while updating passwords in your “main” Bitwarden account.

As an alternative, you could create a free organization vault, and transfer the IOT items into a collection owned by the organization; as organization admin, you can temporarily deny read permissions to the collection for your individual account, at which point the IOT items should be excluded from the Vault Health Reports. This could be a permanent arrangement, in which you change the collection permissions back and forth as needed.