When you add new sub-folders in Asset Bank, you typically want user groups that can see the parent folder to see this new one—i.e., without having to visit every user group manually and set this up.

This happens by default, as subfolders automatically inherit their permissions from the parent folder. Having separate permissions is not ticked.

So adding a sub-folder that does not have its own permissions to my existing 'Coffee' folder, will look like this in each user group.

It does explicitly list the subfolders in folder structures that inherit from the parent. So, any subfolders added will be visible to all groups who have permission to view  (top-level) folder travel.  

Sub-folders with their own permissions

What if I create a subfolder that does have its own permissions (i.e., the 'Has permissions' box above is ticked at the point of creation)? Will existing groups see this new subfolder if they can see its parent?

The answer is yes by default, as there is a global configuration setting that affects this, which is set to true. 

mirror-parent-permissions-on-folder-creation = True
Should new folders be initialised with permissions that match their parent?

So even if you create a new sub-folder with its own permissions, then groups that could previously view or download from the parent folder, will be able to view or download from this folder too.

If you'd prefer this not to happen, and that for new sub-folders you create with their own permissions, you'd like to actually visit and specify the groups who can see them, then we can change the configuration option above to 'False', so that you can do this.

mirror-parent-permissions-on-folder-creation = False

When set to false, sub-folders that are created and inherit permissions from their parent will still function as expected, and all groups that can view the parent folder will still be able to view these sub-folders.

However, sub-folders you create that you tick 'Has permissions' at the point of creation will not be given any permissions in any existing folder. Admin will need to add the newly created folder permission to each group. 

E.g. in the example below I have the setting above set to False. I then create a new RGB Logos folder, tick 'Has permissions', and then click 'Add'. The result is that existing groups will not be able to see this new folder, even if they can see the parent folder. Admins will need to add the newly created folder permission to each group. 

In addition, any new folder that I create that I do not tick 'Has permissions' for, will still inherit from the parent - e.g. I've added the Black & White Logos sub-folder above.

What to watch out for with this approach

If you have an existing folder structure that all inherits from the parent, e.g. my coffee example:

Here, there is a folder structure below this, but as none of the sub-folders have their own permissions, they are not shown.

The sub-folders are:

Coffee

       > Beans

       > Ground

Now, if I decide to add a new sub-folder to 'Beans' called 'Arabica' and want to give them their own permissions for some reason, then this will result in the following changes to existing groups:

I.e. by giving Arabica its own permissions, it also gives its parent folders their own permissions. Groups that can already see the top-level 'Coffee' folder will still be able to see this, and will still see the 'Ground' subfolder. But they will no longer see the 'Beans' sub-folder nor the new 'Arabica' folder.