Admin Menu Editor Pro extends the free version with per-user menu overrides, admin bar editing, plugin page visibility, and import/export. The data still lives mostly inside wp_options on ws_menu_editor, with extra Pro keys for the admin bar tree and per-user overrides. Once a site uses per-user rules ("hide Plugins from this freelancer specifically"), the editor's role-based UI struggles to show you the full picture, because user-level rules sit alongside role-level rules and override them on a per-request basis.

SleekView reads the option keys directly and renders one row per (node, scope) pair where scope is either a role or a specific user. Filters scope the grid to one user's blocked menu, every per-user override defined this quarter, or every admin bar node hidden from non-admins. The plugin page visibility settings stored under the Pro keys show up alongside the main menu rules so an audit can answer the full question, not the partial one.

Inline edits route through Admin Menu Editor Pro's own save path, which invalidates its per-request cached menu so the next admin load reflects the change. Bulk-apply a freelancer lockdown, copy a power-user's overrides to a new hire, or export every per-user override for a change-control review.

Per-user menu overrides are a great idea right up until you have ten of them. A freelancer joins, you hide Plugins specifically from their account, a contractor joins, you hide Tools from theirs, a year later nobody remembers which account has which override. Admin Menu Editor Pro stores all of this carefully in its option keys, but the editor surfaces it inside the role and user editors one subject at a time.

Nobody sits down on Monday and clicks through every user looking for stale overrides. They just leave the overrides in place until something breaks or someone notices during an audit. A grid with one row per (scope, subject, target, action) collapses that audit into a saved view.

Filter scope to user, sort by subject, and you can see in one screen which accounts have overrides that probably should not still exist. Run the view after every offboarding, after every quarterly access review, before any role re-org. The plugin still owns the rules and the cache.

The grid is just the audit surface the editor was never meant to be.