When Selecting folders we only see the logins stored in that particular folder. The logins for Sub Folders are not displayed.
Requested Feature
When Selecting folders we should be able to see Sub-Folder data/logins, maybe with each folder having a separate section in list form. Of course having a toggle to enable this Sub Folder logins visibility on parent folders would be even better, so that if we don’t want this to happen in a particular scenario we can disable this behaviour.
Motivation
I use a lot of nested folders to sort out the passwords. So when I select filter to a particular folder that folder may be pretty much empty since the due to sorting and stuff I have the logins stored in Sub-Folders.
P.S. Another nice thing to have would be a selectable default folder rather than having All logins displayed when logging in.
[Text struck by mod; only one proposal is permitted per feature request.]
Hello,
It is a little bit unclear why you are placing items in subfolders, when you actually want to view all folder items at once. In addition, your P.S. is not helpful to your case, because Feature Request topics must include only a single idea (otherwise it becomes impossible to interpret the meaning of the vote count).
You may want to consider supporting one or more of the following existing feature requests instead:
Well, firstly sorry for the P.S., since it’s not a valid thing. I’ll remember to avoid such practices in future posts.
Secondly going through those three posts, I would say they kind of capture nearly all my requirements. But due to lacking trust level since I am new I can’t upvote.
As for me placing things in subfolder when I want to be able to view them even from the parent folder is because of sorting logins. I have use case of very similar logins on basically the same domain so I use this method to have a clear differentiation between my logins. And to view these logins either I use ‘All Logins’ (which obviously isn’t a good method) or navigate to a specific subfolder 2 levels deep within some folder which stops me from being able to view logins on the same level within a different folder is just not a good experience.
Could you provide a specific example (or a made-up example that illustrates what you’re describing, in case you prefer not to share the actual domains)? What do you mean my “similar logins” (same username and password?)? What do you mean by “basically the same domain” (same base domain but different subdomains?)? What do logins within the same subfolder have in common, and how do they differ? What is different and what is the same about logins that you store in different subfolders within a common parent folder?
When posting domain names for your examples, please enclose them in backticks (`) — e.g., `www.example.com` — so that you don’t run afoul of link posting restrictions for new members.
I’ll edit your post to strike that part, if you don’t mind.
You just need to spend a little more time (<30 min) reading topics and comments of interest to you, then your trust level will be automatically promoted from “new user” to “basic user”, which unlocks your voting privileges.
What I meant when I said, I need to sort login and stuff, was:
Let’s say I serve multiple entities and they all have some data stored with the same company, and each entity can have multiple storages listed with the provider company.
So what I do is, I sort the logins in the way listed below:
Clients
Client 1
Login 1 for Storage 1: The URL that this provides the autofill for is something like www.something.com/abc/xyz/123
Login 2 for Storage 2: The URL that this provides the autofill for is something like www.something.com/abc/xyz/456
Client 2
Login 1 for Storage 1: The URL that this provides the autofill for is something like www.something.com/abc/xyz/789
Login 2 for Storage 2: The URL that this provides the autofill for is something like www.something.com/abc/xyz/150
And so on. So I need to use Match Detection of Starts With since the domain and subdomain are same and sort them into folders for easy access based on the client. And sometimes I want when I select Clients folder to get all the logins within that folder and subfolders in a list with list having subsections like:
Any logins within Clients folder
Client 1
Login 1
Login 2
Client 2
Login 1
Login 2
This would help me avoid changing folder every time I need to see some login data for some specific client.
2nd Answer
I’ll edit your post to strike that part, if you don’t mind.
Sure, go ahead.
3rd Answer
Thank you for the information. I did that and can now give upvotes.
Your example is still a bit too vague for me to fully understand your use-case. Also, it is not clear whether or not the login credentials for “Login 1” are different for Client 1 and Client 2 (i.e., the Client 2 logins are actually “Login 3” and “Login 4”).
Is there a reason why you couldn’t just modify the name of each login item to start with some identifier unique to each client, and then place all logins for this storage provider company in a single folder — as shown below?
Since Starts withalso matches path components (that’s the abc/xyz/123 part), setting the URIs as you proposed would then result in autofill only presenting the one correct entry for that login page, leading me to believe autofill is behaving well in your scenario.
You might also consider voting for the Vault Item Labels (tags) feature request. Effectively, tags are allowing a vault item to be in multiple folders simultaneously, but with no nesting. In this design, you would likely assign both a “storage company” tag and a “Client 1” tag to your first example. And then, when searching you could presumably filter on both tags.
Until tags arrive, I have (mostly) given up on folders, relying on @grb’s naming trick and searching when viewing/editing because being constrained to a single folder is just too constraining. Do note that @grb is referring to the Item name (required) field and not Username. The item name is free-text and can contain whatever makes it easy for you to identify a vault entry.
OK, that’s your prerogative. However, let’s find a better topic title for the feature request, since “folder cascading” is neither standard terminology nor self-explanatory.
How about the following?
“Option to show subfolder contents as groups in folder view”
