Handing a client the full WordPress dashboard can give them more to sort through and more to change than they need. WP ToggleSuite is built to give them a focused workspace while keeping the controls you manage out of their way.
We took a first look at the plugin as a new user, starting with its website and then testing its Client Cleanup and Client Branding modules. The hands-on portion shows what worked in our test and where we still had questions.
Key Takeaways
- WP ToggleSuite lets site managers customize the WordPress admin experience for individual users or roles by adjusting menus, the toolbar, dashboard, notices, updates, editor panels, and branding.
- Client Cleanup includes user and role profiles, menu controls, dashboard settings, notice cleanup, update protection, and a View as Client preview.
- In our test, menu and toolbar changes, a custom dashboard widget, update restrictions, and admin branding appeared in the client preview.
- Update Protection restricts update management for targeted users, but it doesn’t stop update checks or automatic background updates.
A First Look at the WP ToggleSuite WordPress Plugin
What WP ToggleSuite Is Designed to Do
WP ToggleSuite lets you shape the WordPress admin experience for individual users or roles. You can hide or block menu items, adjust the toolbar and dashboard, control notices, and preview what a client will see before you hand over a site.
There are two goals here. Give clients the tools they need to do their work, and protect the parts of the site they don’t need to touch. As an agency owner, we understand why both matter.
This was an unedited, high-level first look at a product we hadn’t used before, not a tutorial. We thank WP ToggleSuite and its founder for partnering with InfluenceWP. Learn more by viewing the WP ToggleSuite listing on our platform.
The Website’s Client Handover Example
The website opens with a visual example we liked. As you scroll, a full WordPress dashboard gives way to a client view with fewer items. It makes the central idea easy to see: decide what stays available, remove what doesn’t, and check the result before the client signs in.
The site lists controls for users and roles, reusable client profiles, the admin menu and toolbar, dashboard layouts and widgets, editor panels, notices, updates, and branding. It also lists export and import, so you can take a configuration you like and use it on another site.
View as Client is an important part of that handover process. You can verify whether you’ve hidden too much or left something visible that you meant to remove. We used that preview repeatedly once we got into the plugin.
The Founder, Changelog, and Documentation
Before opening the plugin, we sought the product pages that help us get a feel for a new tool: information about its creator, a changelog, and documentation.
A Founder Building for a Familiar Need
The site introduced the founder and noted more than 10 years of WordPress experience. He built WP ToggleSuite to address a need he had himself. That caught our attention because we’ve encountered the same client-handover problem in our agency work.
The changelog also showed an active development pace at the time of recording. We saw two updates posted that day, another a few days earlier, and two more shortly before that. Early users appeared to have a chance to share feedback while the plugin was still taking shape.
Support Was Available, but Documentation Was Limited
We tested the site’s chat widget with a question about roles before recording. Our question wasn’t very detailed, so we couldn’t say much about how it would handle a more precise request. At the time of this first look, that widget was the main help option we found.
We’d still like to see fuller documentation on the site. It would provide customers a place to find answers and make those answers easier to surface when someone asks an AI tool about the product.
Pricing, Licensing, and Reusing Settings
The price shown during the recording was $19 as a one-time payment for unlimited sites. That’s the price we saw then, not a promise that it will stay the same.
The account area showed connected sites and a central way to revoke licenses. We could also see the WP ToggleSuite version, the WordPress version, the PHP version, and the date when a site last connected. A download for the latest plugin version was available there too. We noticed a few labels displaying in German.
Inside the plugin, export and import provide a way to reuse your work. You can export settings from one site and import them to another. We raised one longer-term idea with the founder: a central dashboard for rolling out rules across many managed sites. That would be useful when you’re responsible for hundreds of sites, but it was our suggestion, not a feature we tested.
Modules Discussed for the Future
We also spoke with the founder about possible additions. These were plans discussed during the first look, not modules we demonstrated as ready to use:
- Admin Essentials was described as a collection of everyday WordPress admin tools in one modular plugin, rather than a set of smaller plugins.
- Safe Content Editing was a working name for an interface that would let clients update approved content without giving them full access to the page builder, layout, or site structure.
- Staging and Deployments was described as a larger, longer-term idea.
The current modules gave us plenty to inspect. We started with Client Cleanup.
Starting with Client Cleanup
The WP ToggleSuite menu showed the available modules, along with Agency Protection, export and import, and account and update settings. Agency Protection lets you choose which WordPress administrators can continue to manage WP ToggleSuite. That’s useful if a client has an administrator account but shouldn’t be changing the rules you’ve set up.
We activated Client Cleanup and opened its settings. During the demonstration, the online module catalog was unavailable, so we continued with the installed module.
The module opened with a standard profile and Client Mode enabled. Our admin account was kept unaffected by default, which meant we could test client settings without applying them to the account we were using to manage the site.
Profiles for Users and Roles
You can create profiles for different groups, then assign them by role or by individual user. A marketing team, authors, and editors might each need a different view. Direct user assignments override role-based profiles.
We selected a test account with the Editor role. The settings also offered role-based targeting. If you’ve already set up a profile you like, you can copy its settings into another profile and adjust that copy instead of starting over.
Testing the Admin Menu and Client Preview
The Admin Menu screen gave us a working view of the menu items available on the site. Items could be visible, hidden, or blocked. We tested those states with Pages and saw the items move between the corresponding lists.
The controls went further than that. We could reorder items, change their display names and icons, and adjust individual entries. We also created a custom group, added a custom link beneath it, and confirmed that the group and link appeared in the client view. A separate setting controlled how WordPress’s menu-collapse option would appear to client-mode users: in its default position, moved to the bottom, or hidden.
Our test link needed a URL before the settings would save. Once the group and link were saved, they appeared where we expected in the preview.
Checking What the Editor Sees
We used View as Client before making menu changes, then returned to it after saving. The plugin let us open the view as our test editor. We also saw an option to create a private preview link for someone else to test.
When we removed Pages from the editor’s menu and opened the preview again, Pages was gone. That quick review was one of the more useful parts of the walkthrough. We could see the result rather than assume our settings had done what we intended.
The Admin Bar and Dashboard Controls
The next two areas let us work on the toolbar across the top of WordPress and the widgets on the main dashboard screen.
Admin Bar Changes
The Admin Bar settings offered options to hide, rename, and reorder items. We could also add custom links and groups, much like we did in the admin menu.
For a simple test, we hid the “Howdy” greeting from the test editor’s toolbar. After saving and opening View as Client, it was gone. We had initially considered testing a cache item but were caught that we were looking at our admin session and switched to an item we could verify in the editor view.
Dashboard Columns and Widgets
The Dashboard settings offered the WordPress default layout or a chosen column layout. We tested the column control and confirmed that it could force the dashboard into one column. The available choices also included two, three, and four columns.
We added a custom dashboard widget and saw it in the client preview. A support widget or a set of tutorial videos were two possible uses mentioned during the first look.
Some checkboxes beside the detected dashboard widgets were unclear to us. We tried them but couldn’t confirm what they changed, so we still don’t know what they do based on this first look.
Editor Cleanup Needs a Closer Look
Editor Cleanup is intended to remove unwanted editor panels while keeping the fields a client needs. The interface said WP ToggleSuite discovers classic meta boxes after a suite manager opens the corresponding edit screen. We opened content first, then returned to the settings to see what had been detected.
We tried posts and pages, including checks around the excerpt, categories, and featured image controls. We couldn’t confirm whether the client view had hidden the block editor components we were looking at. The settings appeared to distinguish classic meta boxes from other editor components.
We’d like that distinction explained more clearly. Our test didn’t establish a confirmed block editor limitation; we may have missed the relevant control. For a feature meant to protect the editing experience, it would help to know exactly which panels it can manage.
Notices and Update Protection
Notice Cleanup offered three strictness levels: Conservative, Balanced, and Strict. The Conservative description said it hides clear promotional, review, onboarding, and license nags while leaving unknown or potentially important notices visible. We kept notice cleanup on for part of the test.
Update Protection was a separate switch for targeted client-mode users. The settings described restrictions on updating WordPress core, plugins, and themes. They also described removing the WordPress Updates menu, toolbar item, and update counter, along with limiting access to the combined updates screen.
Update Protection doesn’t stop the site’s update checks or automatic background updates. It restricts update management for the targeted users.
We tested that distinction with a separate administrator account added to Client Mode. Before enabling protection, that account could see update information. After enabling it and previewing the account again, the update information we were checking was hidden. Protected accounts remained unaffected.
Branding the Admin and Login Experience
Client Branding was the other module we activated. Its Targeting tab lets us apply branding to all users, selected roles, or an individual user. For the test, we targeted our editor account.
Admin-Area Branding
The backend settings let us upload a custom logo and adjust its height, width, alignment, and vertical position. We could also apply an accent color across the WordPress interface and change menu colors, including backgrounds, text, and icons.
We chose conspicuous test colors so any change would be easy to spot. The module also offered personalized text for the admin footer. After saving, we used Client Cleanup’s View as Client option to inspect the branded admin view.
Login-Screen Branding
The login settings included a live preview. We could adjust the logo, add a background image, change overlay color and opacity, and set colors for the page, form, buttons, text, and links. There were also controls for form-field and button corner rounding, full-width login buttons, the privacy policy link, and the language switcher.
We tried several of those settings in the preview. Some of our test colors weren’t suitable for an accessible final design; we chose them to make the changes obvious. We didn’t complete a separate logged-out browser test of the finished login screen.
One small improvement we’d welcome is a View as Client option inside Client Branding. We could reach the client view through Client Cleanup, but a direct option in the module we were editing would make the review easier.
Final Thoughts on WP ToggleSuite
WP ToggleSuite gave us detailed control over what a client sees in WordPress. We confirmed menu and toolbar changes in the client preview, added a dashboard widget, tested update protection, and inspected the branding options.
A few details still need clearer answers, particularly the dashboard widget checkboxes and editor cleanup in the block editor. Even with those first-look questions, the main handover idea was clear: you can give clients a more focused dashboard and check their view before you pass the site over.
Frequently Asked Questions About WP ToggleSuite
What Does WP ToggleSuite Do?
WP ToggleSuite lets site managers customize what individual users or roles see in the WordPress admin. Its controls include menu items, toolbar settings, dashboard layouts and widgets, notices, update access, editor panels, and branding.
Can WP ToggleSuite Create Different Admin Views for Different Users?
Yes. You can create profiles and assign them to roles or individual users. The first look also found that an individual user assignment takes priority over a role-based profile.
Does WP ToggleSuite Update Protection Stop Automatic Updates?
No. Update Protection restricts update management for targeted users, including access to update controls and information. It doesn’t stop update checks or automatic background updates.
How Much Did WP ToggleSuite Cost During the Review?
The price shown during the recording was $19 as a one-time payment for unlimited sites. That was the price at the time of recording, and the article doesn’t present it as current pricing.