We launched new forums in March 2019—join us there. In a hurry for help with your website? Get Help Now!
    • 4892
    • 7 Posts
    Hi -- I was wondering if there is a way for the parent container to have different access controls than the children resources of this particular container?

    Here's what I'm attempting to do. I want a user group to have permissions to add, edit, delete all child resources in a particular folder(container) but I do not want that same user group to be able to edit,delete the parent. Is there an easy way to do this? I've looked on the web and cannot seem to find a solution. thanks for any help in advance.
      • 28042 ☆ A M B ☆
      • 24,524 Posts
      Which version of MODx?
        Studying MODX in the desert - http://sottwell.com
        Tips and Tricks from the MODX Forums and Slack Channels - http://modxcookbook.com
        Join the Slack Community - http://modx.org
        • 4892
        • 7 Posts
        I'm on the latest release 2.2.6-pl
          • 42562
          • 1,145 Posts
          I think to put the parent in a resource group A of its own,
          put the children in a resource group B of theirs.

          Give access to A to one usergroup
          Give access to B to another usergroup

          This would work perfectly if the resources were already created. I say so because I think the children inherit the resource group their parent belongs to as soon as they are newly created...unless you remember to check the correct resource group.
            TinymceWrapper: Complete back/frontend content solution.
            Harden your MODX site by passwording your three main folders: core, manager, connectors and renaming your assets (thank me later!)
            5 ways to sniff / hack your own sites; even with renamed/hidden folders, burst them all up, to see how secure you are not.
            • 40045
            • 534 Posts
            Good point with the inheritance, that would probably create the need for a plugin that sets the appropriate resource group OnDocFormSave or so for the child resources.

            usergroup B (less rights) should only have permission to VIEW Resource Group A, but not anything else...

            interested if it works =)!