Topic "More Restrictive Permissions on Parent Folder" a message from Kattywumpus

More Restrictive Permissions on Parent Folder then Child folder. After upgrading our enterprise version of RDM to 9.x we ran into a major issue. It appears 9.x RDM no longer allows more restrictive permissions on the parent folder then the child. Our child folders are team or application specific. Example under the default “Session” folder there are three primary parent folders for major groups: Apps, Infrastructure, and Documents. Most users only had view permissions to these three parent folders. Under each parent folder there are many subgroup folders. Key users in each sub-folder have full permissions to the folder to manager the sessions and tools related to their group responsibility. This management strategy work fine in all the previous versions of RDM, but after upgrading to 9.x all users lost add, edit, and delete permissions to their team folder because the parent folder had more restrictive permission of only view. I need to know how to fix this ASAP. I had no choice but to grant all users full permission to the parent folders which has result in other issues due to our large IS staff. For example someone made a copy of &quotGlobal Credential Sets&quot folder under Apps folder. It's a big deal making any major change to our environment since we have thousands of sessions defined. Yes, thousands! Just the parent Apps folder has well over a thousand sessions.


I know about the &quotDeny add entry in the root folder&quot setting but appears to only affect the creation of folders and sessions immediately under the &quotSessions&quot folder. It would be great if the Apps, Documents, Infrastructure folder could be root folders like the default session folder is, but in the previous version this was not changeable. Help!