Nested Vaults (again)

Options
TheG
TheG
Community Member

Can we please add 'Nested Vaults' as a priority feature. Having moved from our previous password manager, I have numerous users asked and berating me for moving to 1Password and not being able to nest faults :)


1Password Version: Not Provided
Extension Version: Not Provided
OS Version: Not Provided
Browser: Chrome

Comments

  • Dave_1P
    Options

    Hello @TheG! 👋

    Thank you for the suggestion! Could you tell me a little more about how you and your users would use a feature like "nested vaults"? Do you require this feature in order to better organize items inside of a vault or to control which team members see which items? If it's the former then have you considered using tags to organize the items instead:

    Once I know more about the use case I can file a feature request on your behalf. 🙂

    -Dave

  • TheG
    TheG
    Community Member
    Options

    Hi Dave
    We, as a company, have several departments, and each department can have a number of department password vaults.
    To try and maintain an organised approach, I have instructed staff to use a naming convention of 'department name' - 'suitable description'
    example: Infrastructure-sharedmailboxes, Support-Clientcontacts
    This allows us to quickly find department folders at a glance, but we will still end up with a single layered long list of vaults.
    It would be much easier for admin and discovery, to have a multi-layer approach, so the top layer could be department vaults, and then all of each departments vaults could all be contained within the departments main fault.
    Much as in the way Windows folders works, we can have each department have a vault, and within, they can have multiple vaults specific to that department.
    Permissions could be applied at the top or individual.
    Thanks
    Glyn

  • Dave_1P
    Options

    @TheG

    Thank you for the detailed description! I've taken your feedback and use case and filed a feature request on your behalf.

    For the time being, your users might find collections to be a useful way to choose what vaults are seen at a given time. For example, a user could create a collection for Department A and then only see vaults that are applicable for that department. You can read more here: Use collections to create custom groups of vaults

    -Dave

    ref: PB-39995816