Vault Naming Convention – Security & Usability Concern

Hello @zondi! 👋

Thank you for sharing your feedback! Last year, we renamed 1Password Teams and Business private vaults to employee vaults to reduce confusion between work and personal accounts. This was done based on feedback from our business owners and admins that users were accidentally saving work items in their personal accounts.

You can read more about employee vaults here: 

• Private vaults in 1Password Teams and Business are now employee vaults
• About your Employee vault

When employees use the 1Password app to save a new item (or edit an existing item), they'll see a breadcrumb which will tell them which account's Employee vault they're saving that item to: 

Users can also choose to just see vaults from a particular account or collection by using the account/collection switcher in the upper left corner of the app: 

Collections can also be used to create groups of vaults for different purposes: Use collections to create custom groups of vaults

This naming convention creates significant ambiguity. Why wasn't a more logical format such as "$AccountName - Employee" considered to differentiate vaults across multiple accounts?

It seems like the breadcrumb that I mentioned above serves this same purpose to let a user know which account's Employee vault an item will be saved to. If there's a use case that I've missed then I'd love to know more so that I can pass this feedback along to the team. 

-Dave

From what I can see, it is 1Password Company > Employee, Company > Employee, NextNextCompany > Employee.

In a high-pressure situation (especially when an engineer or developer is juggling multiple tasks), this similarity makes it easy to mistake one for the other. Unfortunately, in our case, that’s already happened.

To prevent this, 1Password could either use color-coding or make the naming convention more explicit, such as CompanyEmployee. Or even both.