Skip to content

Re-Enable Recursive Shares #4855

Description

@Bibo-Joshi

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

My directory structure:

SheetMusic  # group folder shared with *group* "librarians"
    NewPieces  # folder used for ongoing work by group librarians
    General  # folder containing sheet music relevant for all musicians
    Trombone  # folder containing sheet music relevant for musicians playing trombone
    Tuba  # folder containing sheet music relevant for musicians playing tuba
    ...

I have set up teams/circles (!=groups) for each instrument. I'm choosing those instead of admin-managed groups as it's important that musicians can self-apply to the teams.
My goal to share the tuba directory with the tuba musicians etc.

Describe the solution you'd like
Allow sharing the nested directory Tuba from within the groups folder SheetMusic to teams (and groups) as it was possible in NC32 and prior.

Describe alternatives you've considered
Improve the "Advanced Permissions" to allow granting access to only specific subdirectories. Currently I could grant access for tubist to the SheetMusic directory and restrict access to the NewPieces and Trombone directories, but this is cumbersome for a large number of directories and instruments/teams. Moreover, if the admin-user is a member of the instrument-team (necessary to approve join-requests), I can't remove read-access for that team on a subdirectory. The error message says something along the lines "Can't revoke your own read permissions". So this approach can work only if the owner of the SheetMusic directory and members of the teams have no overlap.

It would good I could disallow tubist from viewing the SheetMusic directory in general and grant access only to the subdirectories General and Tuba.

Additional context
This worked in NC32 and prior. After updating to NC34 the setup is broken and musicians can currently not access their sheet music.

Metadata

Metadata

Assignees

No one assigned

    Type

    No type

    Projects

    Status
    Backlog

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions