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.

room34

NEW IN VERSION 2.0.0: Users with a custom role will now only see the posts or pages they are assigned to. We’ve also streamlined the admin interface for easier configuration, and included additional instructions to help you get the proper capabilities assigned to your custom roles.
Custom Access Roles allows you to create, edit and delete custom roles for editing content. It was created to fill a need for a role editor plugin that is focused on providing easy-to-use admin tools for restricting content editing access. It is not concerned with restricting viewing access on the front end.
It is specifically intended for large sites with multiple content editors, where editors (by role, not individually) need to be restricted to only being able to edit specific areas of the site.
With this plugin, administrators of large sites have relatively fine-grained control over which user roles can edit which content, making it possible to manage a team of editors without concern that they will (accidentally or deliberately) edit content they should not have access to.
You can define a fully customized set of capabilities for each role, along with defining a specific set of post categories, pages, and custom post types to which those capabilities apply. For all other content, the role will have read-only access.
Custom Access Roles provides an easy interface for managing these roles and capabilities, with checkboxes for each capability grouped by the standard roles they’re associated with, plus checkboxes for each post category, page, and custom post type, presented in an organized hierarchy.

Custom Access Roles

Create custom roles with editing capability for only specific pages, categories and post types.

Trilobita Editor Remit vs Custom Access Roles