A few years ago, I migrated all the institutional policies to their own group and similarly all the faculty handbooks to one group (which was a smart thing that makes everything more sane to maintain). These are not normal groups, like the history dept or even the president’s office, but more “admin-only” type content.
So what would be neat is to have these groups sort of “locked down” so only I could edit them or at least I get notified by any edits made to anything within those groups. Thoughts?
We don’t give anyone access to all groups (outside of the web team anyway). All users are limited to editing the groups we assign them to, so these types of “locked down” groups are easy for us. Your setup may look entirely different though.
Some folks use backend.css or backend.js to “soft” disable editing of certain items/fields, even if you have users you may need to have access to those groups for certain reasons. You can use the body class that includes the username to hook into CSS or JS to hide/disable certain fields for everyone but specific editors. More on back-end body classes.
We have things generally locked down, but there are definitely a few admin-level people who with the best intentions might go in there one day to tweak something that really ought to be approved by general counsel et al first.