Skip to content

Handling nested group folders access privileges when groups don't have access to parent folder #2551

@pmarini-nc

Description

@pmarini-nc

How to use GitHub

  • Please use the 👍 reaction to show that you are interested into the same feature.
  • Please don't comment if you have no relevant information to add. It's just extra noise for everyone subscribed to this issue.
  • Subscribe to receive notifications on status change and new comments.

Is your feature request related to a problem? Please describe.

When you give access to a group (or circle) to a nested groupfolder, users in that group cannot see the subfolder unless they manually create the parent folder(s).

Users don't know that and this creates some confusing renaming action if they are later granted access to the parent folder(s).

Describe the solution you'd like
I think that there are three possible expected behaviours:

  • automatic parent folder(s) permission adjustment: apply the minimum set of permissions that allow the users in the group to access the subfolder they have been granted access to
  • mount at root
  • prevent the assignment of privileges to nested groupfolder when the group/circle doesn't have access to the parent groupfolder

To be discussed..

Describe alternatives you've considered

Additional context

Metadata

Metadata

Assignees

No one assigned

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions