KakapoWP KakapoWP
Log in Get Lifetime
Kakapo Roles

Per-user capabilities

One capability for exactly one person.

For the special case that does not warrant a role of its own: a capability on top of the role — or explicitly against it. WordPress stores roles and per-user capabilities in the same row (wp_capabilities); a withdrawn capability therefore beats the role, even the administrator’s. WordPress’s own interface shows none of this.

Get lifetime — €149All Roles features
All nine plugins included in the lifetime deal — every future one too.

Per-user capabilities

One capability per user — on top of the role or against it

ActiveSettings

What per-user capabilities offer

Grant capabilities per user
Withdraw capabilities per user explicitly
A withdrawal beats the role
Every change takes effect at once

Here's how it works

1

Select users

2

Grant or withdraw the capability

3

Look up in the log what was set

FAQ about per-user capabilities

When do I use this instead of a role?
When exactly one person needs exactly one exception. For anything that repeats, a role of its own is the clearer way.
Why does a withdrawal beat the role?
Because both stand in the same row, and an explicit “no” there weighs more than an inherited “yes”. That is WordPress behaviour, not this plugin’s.
Do I see this in WordPress itself as well?
No — and that is precisely why this section exists. In WordPress’s user profile a per-user capability is invisible.

More Roles features

Capability matrix →Assign & migrate →Change log →
Ready?

Roles — pay once, use forever.

All nine plugins for €149 once instead of €13 a month. Secure payment via Stripe. For the first 14 days: problem fixed or money back.

Get lifetime — €149