Signing back into the Community for the first time? You'll need to reset your password to access your account. Find out more.
Forum Discussion
Vault Naming Convention – Security & Usability Concern
The recent decision to name all core vaults as "Employee" in 1Password is highly counter-intuitive and introduces unnecessary risk. In environments where multiple 1Password accounts are used, we've ...
1P_Dave
Moderator
ModeratorHello 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:
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
