Adminimize hides admin UI elements per role across menus, submenus, meta boxes, screen options, dashboard widgets, and the post and page edit screens. Every one of those hide lists lives in wp_options under keys like _mw_adminimize_menu_, _mw_adminimize_submenu_, _mw_adminimize_metaboxes_post_, and _mw_adminimize_dashboard_. The plugin's settings screens spread each rule family across its own tab, with one role-selector per tab, which is fine to configure once and painful to audit after the fact.

SleekView reads those option keys, unpacks the role-keyed arrays, and renders one logical row per (area, target, role, action) tuple. Area becomes a filter (menu, submenu, meta box, dashboard widget, screen option). Role becomes a filter, target becomes a sortable column. Saved views can scope the grid to one role's full lockdown, every meta box hidden from Editors, or every change made since the last access review.

Inline edits route through update_option the same way the plugin's own forms do, so anything Adminimize caches or invalidates internally still happens on save. Bulk hide a meta box across multiple roles, copy a role's lockdown to a new role, or export the full hide map for an internal compliance record.

Adminimize is the WordPress admin hardening tool nobody talks about until something leaks. Every site that takes user roles seriously ends up with dozens of per-role hides spread across menu, submenu, meta box, dashboard widget, and edit screen rules. The plugin gives you a checkbox grid for each rule family, which is fine for setting things up and painful for auditing six months later.

Nobody opens five tabs every quarter to confirm that Subscribers still cannot reach the theme editor. They just assume the rule from last year is still there, until it is not. A flat grid with one row per (area, target, role, action) tuple turns that audit into a saved view.

Filters answer the access-review questions directly: what is Subscriber blocked from, which meta boxes does Editor still see, which rules changed since the last review. The plugin still owns the storage and the runtime. The grid is just the workspace where the team actually verifies that the lockdown still holds.