← All releases

wp-content/plugins/bailiwick/bailiwick.php

Bailiwick

Edit roles and capabilities, and see who is affected before you save.

== Description ==

Role editors let you take a capability away from twelve people with one checkbox and find out on Monday. Bailiwick shows the impact first: how many users hold this role, what they will lose, and which of them logged in this week.

Every change is logged with the user who made it and the previous value, so “who removed edit_pages from Editor” has an answer instead of a theory.

Roles are stored in the database by WordPress, which makes them invisible to version control. Bailiwick exports the current state as a PHP file you can commit and apply on another environment.

== Screenshots ==

Numbered the way they ship in /assets/. Click any one to see it full width.

== Installation ==

  • Install and activate the plugin.
  • Open Users → Roles and read the impact panel before changing anything.
  • Export to PHP once you are happy, and commit it.

Bailiwick never grants itself capabilities. Managing roles requires the capability to manage roles.

== Frequently asked questions ==

Can I break my own access?

It refuses to remove your own ability to manage roles. Everything else it will let you do, with a confirmation.

Does it work on multisite?

Per site, and network-wide for super admin capabilities. Both are labelled clearly because confusing them is the classic mistake.

== Changelog ==

= 3.3.0 =

  • Impact preview showing affected user counts and last-login recency before a change is saved.
  • Audit log entries now record the previous value, not just the new one.

= 3.1.0 =

  • Export roles to a committable PHP file, and apply on another environment.

= 3.0.0 =

  • Rewritten around capabilities rather than roles. Custom roles from 2.x are migrated on activation.