The reason that Carrie has access to the top-level LIS resource gallery is as a resource manager. In MCMS, each channel is tied to a resource gallery, but not every channel has its own resource gallery and, by default, channels inherit the resource gallery of their parent.

So imagine you’re building out the LIS channel tree: you start with /lis, then add /lis/about and /lis/about/hours_maps. By default, all of these channels will use the /lis resource gallery. Now you add some maps to that gallery and put them up on the hours_maps page and a few years later a new editor is assigned to the area and needs to update the map images and there are hundred of items in the root LIS resource gallery and nobody wants to sort through them to figure out what goes where.

So your CMS administrator gives up and just gives Carrie Resource Manager permissions to the /lis resource gallery because he knows Carrie isn’t going to go in and delete all the files.

As I said in the meeting, “When you see the permissions, you’ll see why we won’t be able to just go right out and talk to the people assigned to each area”.