Nested folders in department vaults

Hello @TheG! 👋

Thanks for reaching out! 1Password doesn't have sub-vaults or a folder hierarchy but have you considered using tags?

As long as you don't need to assign different levels of permission to the different collections of items you could have one vault named "HR" and then the following tags for specific items: HR-References, HR-AnnualLeave, and HR-Attendance.

Users could then just view the items with that tag by clicking the tag in the sidebar or by using a search filter in the desktop app: Search in the 1Password app to find what you need

Let me know if that doesn't work for you.

-Dave

Hi Dave,
Tags just dont work effectively.  We need nested folders,  and I am sick of being pestered by our staff for them.

Come renewal, this will be raised as a major issue.

Any news?

Thanks

Please understand, nobody cares about tagging passwords… we need folders, we need structure.  Folders and structure foster self-training.  A new hire to the team can simply navigate the password vault and have a snapshot of the job and structure of the systems.

Folders/subfolders are mandatory in all tools, and if you disagree you are wrong.  If you are going to seriously sit there and correct your paying customers who actually use this tool more extensively than you could ever hope, you’re wrong.

Tags are nice, but tags are not useful.  Listen to your customers.  Paying customers.  What is so complicated here?

Explain to me, technically, why it is not viable for us to have folders/sub-folders (and yes, I feel I need to be explicit because you need to understand folders can and should always have subfolders).

Explain to me what impacts and costs the implementation of folders will have on the 1Password bottom line?

Explain to me how the customer is wrong, and we need to bow to your prowess and intelligence, for we are not worthy of your perspective.

Hudu has folders, you are losing to Hudu - which is an inferior password management solution - because they have SUBFOLDERS!

Explain yourselves.

I have been using 1Password since 2018, so quite some time,

Being forced to use 1Password to manage the Kubernetes and production environment is making me hate 1Password because of the lack of folders (please do not suggest tags… stop don’t).

The lack of permission policy around folders, or even being able to visually structure the whole organization, is sometimes based on such permission policy, is making my life miserable. I can’t take this situation anymore, especially when it is an every day situation.

I would appreciate if you even incrementally start with the Visual aspect metadata, then continue into Permission Policy eventually, I take anything at this point to make my life a little bit less miserable every day ...

I am currently evaluating 1Password and going to be signing my family up to a shared password manager.

I am looking at

• 1Password
• BitWarden
• Keeper

Honestly, the lack of fine grained folder support is a massive deal breaker for me, something which the other 2 seem to have build in.

As I would be using it for personal and private use, I have an agency with clients and I want to be able to put all the logins associated with a certain client into a folder and be able to share all of that if I need to. Having to put it into 1 Vault and then Tag it does not solve the issue from what I can tell, as you can’t share out all the ones Tagged with a certain value.

I too share in the OP’s frustration around what I would expect to be common place with managing passwords, not just 1 big Vault or just create multiple vaults and end up having to give them really long names and end up with a massive list.

I unfortunately cannot proceed with 1Password and will have to continue evaluating the others