Description

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:

A university with departments each managing their own news and pages
A company where different teams own different sections of the site
An agency managing a client site with multiple editors who should not have access to each other’s content

How it works

Once a user has permitted categories assigned, Remit:

Filters the post and page list screens to show only content in their permitted categories
Restricts the category selector in the block editor to their permitted categories only
Blocks any attempt to save content outside their permitted categories — enforced server-side, not just in the UI
Allows access to uncategorised content (posts or pages with no categories assigned) so nothing is inadvertently locked away

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.

Screenshots

Editor Remit section on the user profile page (as admin) — assign permitted categories per user
Settings page (as admin) — enable category support for pages
Post list filtered to show only permitted categories (as restricted editor)
Block editor with category panel restricted to permitted categories (as restricted editor)

Installation

Search for Trilobita Editor Remit in the WordPress plugin directory under Plugins > Add New
Click Install Now and then Activate
Go to Users > Editor Remit and assign permitted categories to editors and authors
Optionally enable category support for pages under Settings > Editor Remit

FAQ

Does this affect administrators?: No. Administrators are always unrestricted regardless of any category assignments.
What happens if a user has no categories assigned?: No restriction is applied. The user behaves exactly as they would without the plugin active.
Can restricted users see uncategorised posts and pages?: Yes. Content with no category assigned (or only the default Uncategorised category) is always visible to restricted users. However, they must assign at least one of their permitted categories before saving.
Does it work with the block editor (Gutenberg)?: Yes. The category panel is filtered in real time and saves are validated server-side via the REST API.
Does it work with the classic editor?: Yes.
Can I restrict pages as well as posts?: Yes. Enable Settings > Editor Remit > Enable categories for pages. This adds category support to pages and applies the same restrictions there.
Does it support custom post types?: Not in the current version. Remit restricts posts and optionally pages only.
Does it support tags or custom taxonomies?: No. Remit works with the built-in category taxonomy only.
Will it work on a multisite installation?: Remit has not been tested on multisite and does not officially support it in this version.
Where do I assign categories to a user?: Two ways: go to Users > Editor Remit for a summary of all editors and authors with inline editing, or go to an individual user’s profile page and scroll to the Editor Remit section.
Restrictions are not applying to a user — what should I check?: Confirm the user has the Editor or Author role. Contributors, subscribers, and administrators are never restricted. Also confirm at least one category is assigned to the user — a user with no categories assigned is unrestricted by design.
A restricted user can see posts they should not be able to see: Check that those posts have a category assigned. Uncategorised content (posts with no category, or only the default Uncategorised category) is intentionally visible to all restricted users.
Saving a post is blocked unexpectedly: A permitted category must be assigned before publishing. Saving as a draft does not require a category. If only the default Uncategorised category is selected, publishing will be blocked — assign one of the user’s permitted categories first.
Page restrictions are not working: Go to Settings > Editor Remit and confirm Enable categories for pages is checked.

Reviews

There are no reviews for this plugin.

Contributors & Developers

“Trilobita Editor Remit” is open source software. The following people have contributed to this plugin.

trilobita

Translate “Trilobita Editor Remit” into your language.

Interested in development?

Browse the code, check out the SVN repository, or subscribe to the development log by RSS.

Changelog

1.0.11

Documentation update: corrected installation instructions and listing copy now that the plugin is live on WordPress.org

1.0.10

Users menu item renamed from “Category Restrictions” to “Editor Remit” for clearer plugin attribution
Settings page now shows an info notice linking to Users > Editor Remit
Plugin name used as section heading on user profile page (standard WordPress convention)
Summary page heading changed to “Editor Remit” with “Category Restrictions” as subtitle
Restriction notices now prefixed with “Editor Remit:” so users know which plugin is acting
Admin styles moved to a dedicated stylesheet for better maintainability

1.0.9

Fix: add sanitize_text_field() wrapping wp_unslash() in nonce verification calls
Fix: exclude WordPress.org directory assets (banners, icons, screenshots) from release ZIP
Fix: release ZIP renamed to trilobita-editor-remit.zip to match WordPress.org expectations

1.0.8

Plugin renamed to Trilobita Editor Remit; text domain updated to trilobita-editor-remit

1.0.7

Fix: replaced inline script blocks on the user profile and summary pages with properly enqueued assets via wp_enqueue_script()

1.0.6

Block editor: non-permitted category checkboxes are now visually disabled and greyed out rather than silently reverting when clicked
Fix: opening a post with only Uncategorised assigned no longer triggers a false “categories removed” notice
Fix: Uncategorised checkbox is greyed out to signal it is not a valid choice, but remains untickable so users can remove it when assigning a permitted category

1.0.5

Block editor now shows a notice when a non-permitted category is removed
Classic editor error notice is dismissible and includes a Continue editing link
Minor label and copy consistency fixes

1.0.4

Draft posts saved via the REST API now have unauthorised categories stripped silently rather than returning a 403 error, matching classic editor behaviour
Category Restrictions summary page under Users menu with inline editing (collapsed by default, expand per row)
Category Restrictions column added to the Users list screen
User profile page now shows categories hierarchically with Select all / None links; read-only view uses pill tags instead of disabled checkboxes
Settings link added to the Plugins list page
Fix: summary page Save button now redirects correctly (was clearing page content)
Fix: cache invalidation scoped to controlled post types and category taxonomy only

1.0.3

Plugin renamed to Editor Remit; slug changed to editor-remit

1.0.2

Fix: block editor no longer blocked on first load (auto-draft false positive)
Fix: REST updates to published posts now correctly enforce category requirement
Fix: default Uncategorised category no longer triggers a false restriction block
Fix: classic editor violations save as draft with admin notice instead of wp_die()
Fix: unauthorised taxonomy terms stripped after classic editor save

1.0.1

Fix: contributors no longer incorrectly caught by restrictions
Added GDPR personal data export and erasure support
Allowed-post-ID results cached per user to reduce database load

1.0.0

Initial release
Restrict editors and authors to specific categories
Block editor (Gutenberg) and classic editor support
Optional category support for pages
Server-side enforcement via REST API and wp_insert_post_data

Description

Screenshots

Installation

FAQ

Does this affect administrators?

What happens if a user has no categories assigned?

Can restricted users see uncategorised posts and pages?

Does it work with the block editor (Gutenberg)?

Does it work with the classic editor?

Can I restrict pages as well as posts?

Does it support custom post types?

Does it support tags or custom taxonomies?

Will it work on a multisite installation?

Where do I assign categories to a user?

Restrictions are not applying to a user — what should I check?

A restricted user can see posts they should not be able to see

Saving a post is blocked unexpectedly

Page restrictions are not working