trilobita

Editor Remit gives administrators fine-grained control over which categories editors and authors can work in. Assign permitted categories to a user and they will only see and edit content within those categories — nothing else.
Who is it for?
Organisations and agencies managing WordPress sites with multiple contributors across distinct content areas. Common examples:
<ul>
<li>A university with departments each managing their own news and pages</li>
<li>A company where different teams own different sections of the site</li>
<li>An agency managing a client site with multiple editors who should not have access to each other’s content</li>
</ul>
How it works
Once a user has permitted categories assigned, Remit:
<ul>
<li>Filters the post and page list screens to show only content in their permitted categories</li>
<li>Restricts the category selector in the block editor to their permitted categories only</li>
<li>Blocks any attempt to save content outside their permitted categories — enforced server-side, not just in the UI</li>
<li>Allows access to uncategorised content (posts or pages with no categories assigned) so nothing is inadvertently locked away</li>
</ul>
Restrictions apply to users with the Editor or Author role only. Administrators are always unrestricted.
If a user has no categories assigned, no restriction is applied — they behave as normal.
Page support
By default WordPress does not enable categories for pages. Editor Remit includes an optional setting to add category support to pages and apply the same restrictions there too. Enable it under Settings > Editor Remit.
Block editor (Gutenberg) support
Remit works fully with the block editor. The category panel is filtered in real time to show only permitted categories. Saves are validated server-side via the REST API.
Lean and focused
Remit does one thing well. It does not touch custom post types, custom taxonomies, tags, or any other content type. There are no complex role matrices, capability editors, or access control lists to configure.
Current limitations
Remit restricts posts and optionally pages only. Custom post types, custom taxonomies, and multisite installations are not currently supported.

Trilobita Editor Remit

Restrict editors and authors to specific categories for posts, and optionally pages. Simple, focused, no bloat.

Gregory Cornelius

Inderpreet Singh

Mike Burns

Andrew Bauer

Anton Kachurin

BU Section Editing provides advanced permissions for managing the editors on your website team. Create “section editing groups” and granularly control who can edit what content. Assign editors the new Section Editor role, and define what the group can edit with an innovative new interface for specifying any of your content – pages, posts, or any custom post types – right down to the single page or single post level.
The plugin was written by <a href="http://www.bu.edu/tech" rel="nofollow ugc">Boston University IS&T</a> staff with design and UX support from the <a href="http://www.bu.edu/id" rel="nofollow ugc">Interactive Design</a> group in Marketing & Communications.
<h4>Features</h4>
<ul>
<li>Group users with similar editing privileges into “Section Groups”</li>
<li>Each section group can have a unique ACL to determine what content is considered editable for group members</li>
<li>Supports custom post types</li>
<li>Integrations with navigation management views provided by the <a href="https://wordpress.org/extend/plugins/bu-navigation" title="BU Navigation Plugin" rel="ugc">BU Navigation Plugin</a></li>
</ul>
For more information check out <a href="http://developer.bu.edu/bu-section-editing/" rel="nofollow ugc">http://developer.bu.edu/bu-section-editing/</a>.
<h4>Developers</h4>
For developer documentation, feature roadmaps and more visit the <a href="https://github.com/bu-ist/bu-section-editing/" rel="nofollow ugc">plugin repository on Github</a>.

BU Section Editing

Advanced content editing workflow in WordPress through the use of section editing groups and permissions.

Trilobita Editor Remit vs BU Section Editing