Immutable folder structure

Hi,

For my org I'd like to set up a Team folder with a fixed skeleton of subfolders that cannot be removed.

So I have a structure like:

- Team folder
   - Subfolder1
   - Subfolder2
   - Subfolder3
     - Subsubfolder31
     - File31
     - File32

Where Team folder has Read, Write, Share permission but not Delete. The Subfolders themselves should not be Deletable. But inside the Subfolders, team members should be able to freely Delete files and folders (in addition to the other permissions).

The only way to get close to that is to set the Team folder with all three permissions Write, Share, Delete and enabling Advanced Permissions. In the files view I can then set the Advanced Permissions on the Team folder itself to Deny Delete.

For each of the Subfolders I can then choose between Allow Delete (which also allows deleting the Subfolder) or Deny Delete (which means the Subsubfolders and Files inside those folders cannot be deleted). I have a limited amount of Subfolders so I can modify the permissions of each of them. But I cannot at the same time protect the folder and allow users to freely work inside them.

There are some similar issues and requests and I found a lot of other "old" discussions about this topic. For my org this would be a very valuable enhancement to protect from users accidentally moving or deleting important folders.
3649
keeping-the-nextcloud-folder-structure-safe-from-user-editing-deletions

As in the referenced issue 3649 it would be nice to have separate permissions for the folder (not inherited) and the content of the folders (inherited).

As an alternative the subfolders should respect the permissions of the higher folder, and the permissions of the subfolders should only apply to the content, not to the subfolder itself.

It seems like some created a solution for this, organization_folders but it seems like a small team's effort and not up to date (only up to Nextcloud 32).

Nextcloud 33.0.3
Team folders 21.0.7

Start by reviewing the current Advanced Permissions behavior described in the issue and the related discussion in issue 3649. Compare the existing folder and content permission handling with the requested distinction between protecting folders and allowing deletion within them; done means the fixed skeleton remains protected while permitted users can still manage files and nested folders.