Show Folder Hierachy on shared folders/password

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.
1 Like

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.

1 Like

Good morning, I also have the same requirement expressed by mbelsis, are there any updates on this?