I really did like concrete5, I really did, but I've spent as much time now trying to sort out the spaghetti monster that is permissions as I did making a custom template and building the front end of the site.

There are far too many places to edit permissions and there is no map that lays out in detail which settings override which and how.

Would someone please care to render a hierarchy of overrides for permissions please?

For example, I can set permissions per block on the page, I can set permissions on the page, I can set permissions on the defaults of the page type, I can set permissions apparently via php (though it's unclear how or where) or I can set permissions via the site map. Which toggled element prevails and how through that labyrinth of options, please explain.

I have a test site. I replicated the same exact permissions settings on a remote site but the resulting behavior is completely different and absolutely unworkable. My biggest problem now is that everything I've disallowed in the dashboard shows up as a link regardless, yet when clicked just logs the person out. This does not happen in the test site. WHY IS THAT HAPPENING? What small toggle in the myriad of toggles I've already processed is causing such a mess? Please help.

Please consider providing one interface for permissions that begins with the user group or user and then lists the site's functions with a simple yes or no option. Thanks.