Q1. What is the problem that you are trying to solve?
We are using Passbolt with a company-wide predefined folder structure. If I share a password or folder at the lowest levels (our structure follows: [Customer-Name] → [Project-Name] → Application | Operations), users cannot see the hierarchy where they have permissions. For example, if the “Operations” folder is shared with my operations team, they will see multiple “Operations” folders but won’t know which project or customer they are associated with.
Q2. Who is impacted?
Everyone using a similar folder structure in their organization.
Q3. Why is it important and/or urgent?
It improves convenience and simplifies permission management. Instead of sharing multiple levels (Customer → Project and then restricting permissions at the lowest level), we only need to share one folder per project, making the process more efficient.
Q4. What is your proposed solution? (optional)
As a Project Manager, I want to set permissions at the lowest necessary level to streamline permission management.
As a User, I want to see the full folder hierarchy so I can identify which customer and project my “Operations” or “Application” folder belongs to.
we have the same problem … it is really annoying … we will have to change the whole folder architecture just to accommodate this .. There should be a checkbox (i.e. don’t propagate) so that the changes made in the sharing of a folder are not propagated to the subfolders) strange though that when you try to drag and drop a folder on to inside of another folder you get the message to keep the permissions or change the permissions … so the functionality is there
Yes this is something we are aware of and wants to solve with new sharing strategy where from the scenario you describe you will give the possibility to have a folder path from root to the shared folder without reveling whats inside the parent folders. no ETA for the moment unfortunately.
Hello, we would also be very interested in this feature, or something like it.
The use case is that we have a bunch of well-structured folders, often with several levels of subfolders. When we want to share a deeply-nested password, it would be ideal if path/folder structure shows up just like we designed it and the password isn’t just thrown in that person’s root folder.
I’m aware that you can already achieve something like this by explicitly sharing every ancestor folder also with that person. The password will then automatically show it in the correct folder like it does for the rest of the team. That’s great.
However, the crux with this is that whenever you share a folder, it always recursively applies the folder permissions to all entries and child folders. So by adding read permissions for the new person, they can now (at least temporarily) read everything in that folder, not just the specific path you want them to see.
I cannot overstate how undesired this can be.
I simple fix might perhaps be to add checkboxes when setting the folder permissions like “Apply to direct entries“ and “Apply recursively to child folders“ (as another commenter above me said). You could leave both enabled by default, so the current behaviour isn’t changed as long as the user doesn’t intentionally untick them.
This would allow us to very selectively share the path to deeply-nested passwords/folders without exposing everything else along that path.
