Welcome to the official documentation for Plugixa Advanced User Role Editor,
shown in the WordPress admin as Plugixa Role Editor. It is a role and
permission editor for WordPress that describes each role in a sentence you can
read, lets you change it with plain choices such as Their own or All, and
keeps a restore point for every change so that anything can be undone.
The plugin works entirely inside the WordPress admin. It has no front end, no
shortcodes and no blocks.
The plugin ships in two editions:
- Free - a page per role with permission levels, the New role wizard, a
page per person with ordered roles and extra permissions, Compare roles,
Check access, the permission health check, login redirects, History with
restore points, export and import, and the All permissions screen.
- Pro PRO - everything in Free, plus Admin menu control, Screen
clean-up and the Activity log.
Nothing in the free edition is switched off or limited. See the complete
Free vs Pro comparison.
What makes it different
Editing roles is how sites get broken, so a few decisions shape every screen.
They are worth knowing before you change your first role.
| Decision |
What it means for you |
| Nothing is saved until you review it |
Every edit, to roles and to people, waits in one Unsaved changes bar at the bottom of the screen. The bar counts the edits and the people they affect. Review and save lists each change in words before anything is written. |
| A restore point is taken first |
Every save, delete and import takes a restore point before it writes. History lists each one as a sentence, and restoring a point puts roles and the people it changed back as they were. The first restore point is your site before the plugin was installed. |
| Levels instead of checkboxes |
Content permissions are choices such as Write and edit: None, Their own or All. A role that matches no level is shown as Custom with the exact permissions, never as the nearest level. The real capability names stay visible underneath. |
| You cannot give away what you do not hold |
Nobody can grant a permission they do not hold themselves, or hand out a role that contains one. This is checked on the server for every way of writing a change. |
| You cannot lock yourself out |
A change that would remove your own access to the editor is refused with the reason. On a single site, the last administrator cannot be demoted and the Administrator role cannot be deleted. |
| Full control is called out |
Permissions that amount to control of the site are marked Hands over the site. Granting one asks you to type the name of the role or person receiving it, and the server checks that confirmation too. |
| The later role wins |
When someone holds several roles that disagree, WordPress uses the one that comes later on the account. The plugin follows the same rule everywhere and lets you change the order. |
Key concepts
| Term |
What it is |
| Role |
A named set of permissions. Everyone with the role gets exactly these. |
| Permission |
One thing a role or person may do. Each has a plain label and, underneath, the WordPress capability name. |
| Level |
A plain choice for content: None, Their own or All for writing and deleting, Yes or No for publishing and seeing private items. |
| Custom |
Shown when a role’s permissions for one kind of content match no level. The differences are listed. |
| Allowed / Not set / Blocked |
The three states a single permission can have. A block takes the permission away even when another, earlier role on the same account gives it. |
| Extra permissions |
Permissions allowed or blocked on one person’s account, on top of their roles. |
| Full control |
The badge on a role that can do anything on the site, including changing who else can. |
| Can take over the site |
The badge on a role holding at least one permission that leads to administrator access. |
| Unsaved changes |
The bar holding every edit you have made and not yet saved, across roles and people. |
| Restore point |
A copy of the roles, and of the people a change touched, taken before a save. Listed in History. |
| People |
The user accounts on the site, as the plugin lists them. |
Getting started
| Section |
Description |
| Getting Started |
Install, activate, and make and undo your first change |
| Home |
The opening screen: counts, health, the last change and every role in a sentence |
| Free vs Pro |
What each edition contains |
Roles
| Section |
Description |
| Roles |
The list of roles, their badges and who holds them |
| Creating a role |
The New role wizard: start from a job, a copy, or nothing |
| Editing a role |
Levels, switches, Details, and the review step |
| Compare roles |
Every role side by side, with Only differences |
| All permissions |
Every capability on the site and what registered it |
People
| Section |
Description |
| People |
Roles in order, extra permissions, and moving people between roles |
| Check access |
Whether someone can do something, why, and what would change the answer |
Admin area
Safety
Moving and configuring
For developers
Support
System requirements
- WordPress: 6.5 or higher
- PHP: 8.2 or higher
- Browsers: a current version of Chrome, Firefox, Safari or Edge. The
editor is a JavaScript application and needs JavaScript switched on.
Roles and permissions are WordPress’s own data. The plugin changes them through
WordPress’s role functions, so they stay as you left them if the plugin is
deactivated or removed.
Getting help
- Check Troubleshooting first.
- Read the page for the screen you are using.
- Contact support through your Plugixa account.
License
Plugixa Advanced User Role Editor is licensed under the GPL v2 or later. Pro
features require a valid Plugixa licence, managed through Freemius.
