# Admin Menu Editor

Source: https://pluginsuggest.com/plugins/admin-menu-editor/

## Plugin Health & Stats

- Checked 2 days ago

- Source: [WordPress.org](https://wordpress.org/plugins/admin-menu-editor/)

Active installs

 **300,000+**  (Official WordPress.org tier)

WP.org rating

 **4.6/5**  (312 ratings)

Version

 **1.15.3**  (Current repository release)

Last updated

 **2 days ago**  (Nov 16, 2026)

Total downloads **8,456,096**

Tested with WP **7.1.4**

Requires WP **5.9+**

Requires PHP **7.4+**

Support resolved (2 mo.) **0 of 3 (0%)**

Plugin age **16 years, 11 months**

Updates observed **1**

Tracking since **Sep 12, 2026**

## Historical overview

 364-day WordPress.org history

 **Download trend** Daily package downloads · last 90 days

  (7d) **107,352**   (30d) **154,870**   (90d) **338,993**   (Peak day) **56.5K** *Nov 16*

 **Active version adoption** Current usage share

-  **1.15**  60.0%

-  **1.12**  11.9%

-  **other**  9.5%

-  **1.14**  7.0%

-  **1.9**  6.4%

 **Quick take:**  One of the most practical dashboard-cleanup tools for agencies, especially when client users need a simplified admin experience.

 **Best fit:**  Agencies and multi-user sites that need a cleaner WordPress dashboard with controlled menu visibility and permissions.

## Cleaning up WordPress admin without changing the site front end

Client and multi-user WordPress sites often expose more dashboard menus than each role needs. Admin Menu Editor lets an administrator reorganize that interface, but it is important to separate visual hiding from actual WordPress capabilities and permissions.

## Features that matter for this plugin

- **Drag-and-drop menu ordering:**  Dashboard menu items and submenus can be reordered so the admin interface follows the team’s actual workflow.
- **Labels, icons, and destinations:**  Menu titles, URLs, icons, and related presentation settings can be changed without rebuilding the admin menu in custom code.
- **Capability-based access:**  Menu visibility can be tied to required capabilities, which is more meaningful than simply moving an item out of sight.
- **Custom menu items:**  Administrators can add links to internal admin screens or external resources when a client dashboard needs a more guided structure.
- **Redirect and access tools:**  The plugin also includes login/logout redirects and selected content-access controls beyond simple menu ordering.

## Who this fits best

Agencies and multi-user sites that need a cleaner WordPress dashboard with controlled menu visibility and permissions.

Fine-grained dashboard organization. Useful for client-facing WordPress installs. Can reduce accidental access to sensitive screens. These strengths matter most when they align with an existing operational need.

### Choose this plugin if

Agencies and multi-user sites that need a cleaner WordPress dashboard with controlled menu visibility and permissions.

### Keep the stack simpler if

Single-admin sites where the default dashboard menu already works well.

## Trade-offs to consider

Hiding a menu is not the same as removing the underlying capability. Over-customized dashboards can confuse future maintainers. Test these constraints on staging before rolling the plugin across an important production site.

## Free vs paid

The WordPress.org plugin provides a free entry point. Upgrade only when a specific premium capability solves a limitation you have actually reached.

## How I would configure a client dashboard

I would design the menu around user roles, not around what looks cleaner for the administrator account. Test each role separately, confirm that restricted users also lack the underlying capability where appropriate, and document custom menu changes so future administrators understand why the dashboard differs from a default WordPress install.

## What to compare before choosing

For deeper role and capability management, compare it with PublishPress Capabilities or Members. Admin Menu Editor is strongest when the primary problem is dashboard organization and menu access rather than a complete permissions model.

## Practical decision notes

Admin Menu Editor can improve a client dashboard dramatically, but it should be governed like any other permissions-related customization. I would keep a full administrator account with the standard capability set, test client or staff roles in separate sessions, and avoid hiding critical maintenance screens from the people responsible for the site. For agencies, the biggest benefit is consistency: a repeatable admin layout can reduce client confusion across many sites. The risk appears when each site gets an undocumented one-off dashboard that another administrator cannot understand later.

On agency sites, I would also keep an untouched administrator role as a recovery path in case a menu or capability rule hides a screen needed for maintenance.

## PluginSuggest verdict

One of the most practical dashboard-cleanup tools for agencies, especially when client users need a simplified admin experience.

## Admin Menu Editor FAQs

### Does hiding a menu remove a user’s WordPress capability?

Not necessarily. A hidden menu can disappear from the interface while the underlying capability still exists. Sensitive access should be controlled with capabilities, not visual hiding alone.

### Can Admin Menu Editor reorder WordPress dashboard menus?

Yes. Drag-and-drop menu and submenu ordering is one of its core functions.

### Can I rename admin menu items for clients?

Yes. Menu titles and other presentation details can be customized.

### Can different user roles see different menus?

The plugin can control menu access through capabilities, and its Pro version adds more granular role- and user-specific options.

### Is Admin Menu Editor free?

A free version is available on WordPress.org, with additional controls in the Pro edition.

### When should I use a role editor instead?

Use a dedicated role/capability tool when the real requirement is authorization across WordPress, not just a cleaner admin menu.
