We need more granular permissions to control who is allowed to create and edit additional content now that so many options to edit both the staff interface and the OPAC continue to be moved out of systems preferences. The only permission is edit_additional_content and it's all or nothing. It's one thing to allow a branch manager to add some news to the staff interface for their branch. It's another thing entirely to allow them to create and edit information that will display everywhere, or damage (intentionally or not) pages and content created by others. 

I suggest there be 2 new permissions that allow editing News items in the staff interface. One permission would be to edit their own library's News e.g. edit_own_news and the other to edit all News items e.g. edit_any_news.

Creating or editing any other type of additional content would be reserved for those with the edit_additional_content permission.

Bug 35693 Granular Permissions to Everything also mentions this issue, but appears to be intended to encourage developers to remember to address permissions issues when rolling out enhancements and new features.