Thank you for all of the suggestions and interesting discussions.
Here are a couple of updates and clarifications:
(Spaces have been entered to avoid creating links.)
-
I did change the item name from “bitwarden. com” to "vault.bitwarden. com. So login titles of “bitwarden. com” and “community.bitwarden. com” are not used in the Vault.
-
I have decided to put the login for bitwarden. com in the Vault – that is my decision.
-
When I login to the Community, I enter the separate password for the community, not the vault.
-
I am then asked if I want to save the “Update” to the vault, which brings up the item record for “vault.bitwarden. com”.
-
If I enter the password for Community, it would update the record for the Vault – leaving it as an incorrect record.
WHY does Bitwarden not separate the Vault and Community records, since it requires the Community to be a separate login and password?
It seems to me that since login information for “bitwarden. com” and “community.bitwarden. com” do not exist in the vault, creating a new item in the vault should be the natural effect of what is required to happen for the Community login – not revising or updating the item titled “vault.bitwarden. com”.
This seems to me like a “bug-not a feature” instead of “a feature-not a bug” situation. If a separate login and password are required for the Community, then Bitwarden should not be asking to update the Vault record. The two are required by Bitwarden to be separate. A new record for the login community.bitwarden. com should be automatically created.