What a useful CMS should refuse to do

A mature content system needs boundaries as much as it needs features.

Refusal creates legibility

Some actions should be explicit, some should require a stronger permission and some should remain outside the content layer entirely.