Forum Discussion

zondi's avatar
zondi
Occasional Contributor
2 months ago
Solved

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 observed that users frequently misplace credentials in the wrong "Employee" vault. As a result, sensitive data—including API keys, passwords, and banking details—has been inadvertently exposed to unintended users with access to these vaults, despite the correct Primary Vault being set.

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

linux
macos
vault management
  • 1P_Dave's avatar
    1P_Dave
    2 months ago

    Thank you for the feedback! Renaming 1Password Teams and Business private vault to employee vaults was done to reduce confusion between work and personal accounts and I'll let the team know that you'd like to see further steps taken to reduce the confusion between multiple work accounts as well. 

    -Dave

    PB-47091914

3 Replies

Sort By
  • zondi's avatar
    zondi
    Occasional Contributor
    2 months ago

    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.

    • 1P_Dave's avatar
      1P_Dave
      Icon for Moderator rankModerator
      2 months ago

      Thank you for the feedback! Renaming 1Password Teams and Business private vault to employee vaults was done to reduce confusion between work and personal accounts and I'll let the team know that you'd like to see further steps taken to reduce the confusion between multiple work accounts as well. 

      -Dave

      PB-47091914

  • 1P_Dave's avatar
    1P_Dave
    Icon for Moderator rankModerator
    2 months ago

    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: 


    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