Give some roles a clean admin screen
Disable Admin Notifications by Role silences the colored notice boxes that plugins and WordPress itself stack at the top of every admin screen, for whichever roles don't need to see them.
- Choose exactly which roles keep a quiet dashboard.
- Covers standard notices, multisite user notices and network admin notices.
- Works with any registered role, not just WordPress's built-in five.
- Zero overhead for a site that leaves every role unaffected.
What does Disable Admin Notifications by Role do?
When the disable_admin_notifications_by_role module is active, TOWP_Disable_Admin_Notifications_By_Role removes WordPress's four notification hooks, admin_notices, all_admin_notices, user_admin_notices and network_admin_notices, for any role selected in the settings. The check runs on admin_init at high priority, before the notices themselves would normally render, and applies as soon as the logged-in user's role matches one of the selected roles. Because the roles come directly from whatever's actually registered on the site, any custom role gets the same option automatically, right alongside WordPress's standard five.
One notice, relevant to one role and noise to the rest
Since WordPress shows the same notices to every logged-in role, whether a message actually applies to that person or not rarely factors in.
The same notices reach every role
WordPress and its plugins show the exact same stack of notice boxes to whoever's logged in, whether that person is the one who'll actually act on a plugin update or a license renewal or not.
A cluttered dashboard buries what actually matters
A shop manager or a content editor rarely needs to know about a plugin's new version, yet the notice takes up the same space at the top of their screen as it does for an administrator.
A clean screen for the roles that don't need the noise
The module silences the entire notice stack for chosen roles, while leaving it fully intact for everyone else.
Choose exactly which roles go quiet
Select any combination of roles, Administrator included, and every notice on their admin screens disappears.
Every kind of admin notice covered
Standard notices, network-wide notices and multisite user notices all get removed together, not just the most common type.
No effect unless a role is actually selected
With nothing configured, the module doesn't even register its own hook, so an untouched site pays no cost for the feature existing.
Complete coverage, zero idle overhead
Every capability below is present in the supplied PHP class and its settings registration.
Any registered role, checked individually
The role list comes from whatever's actually registered on the site, so a custom role gets the same toggle as any of WordPress's standard five.
Standard, network-wide and multisite
admin_notices, all_admin_notices, user_admin_notices and network_admin_notices all get removed together for a matching role.
High priority on admin_init
The removal runs at priority 999 on admin_init, ahead of when notices would normally print, so nothing flashes on screen before disappearing.
No role is automatically exempt
If Administrator is the role drowning in notices on a particular site, it can be selected exactly like any other role.
The hook only registers if a role is selected
With no role checked, the module never adds its admin_init callback at all, adding nothing to a site that isn't using the feature.
Checks every role a user actually has
Role matching runs through the same towp_user_roles filter a Multi Role module can extend, so a user with more than one role gets evaluated against all of them.
Where a quieter dashboard helps most
The module supports any site where notices meant for maintainers reach roles who have no use for them.
Shop managers and content roles that don't manage plugins
Keep plugin update and license notices out of the way of roles whose job has nothing to do with maintaining the site itself.
Editorial roles focused purely on content
Give writers and editors a clean, distraction-free dashboard, leaving maintenance notices for whoever actually handles them.
Client sites where only the agency manages plugins
Silence notices for the client's own roles, so update and configuration messages stay visible only to the team actually responsible for them.
Quiet where it helps, loud where it matters
The module combines a genuinely cleaner dashboard with zero cost for roles left untouched.
Nothing runs unless a role is selected
The verified implementation stays entirely dormant until configured.
No hook registered without at least one role selected
The module adds no admin_init callback at all until at least one role has been chosen in settings.
One role comparison per admin page load
Checking whether the current user's roles match a selected role is a simple in-memory comparison, not a database query.
Removal happens once, early in the request
Since the notices get removed at admin_init, nothing related to them runs later in the page lifecycle for an affected role.
A deliberate role choice, nothing hidden by accident
The code respects roles exactly as WordPress defines them and changes nothing beyond notice visibility.
Doesn't hide security-relevant information from anyone who should see it
The module is a role selection made deliberately by an administrator, not a way for a lower-privileged role to hide notices from itself.
Configuration requires the same access as any other setting
Choosing which roles go quiet happens through the standard TheOneWP settings screen, available only to an administrator.
Removal is complete, not selective, for a chosen role
Once a role is selected, every notice gets removed for it; there's no per-plugin exception list to review for unexpected gaps.
Respects roles exactly as WordPress defines them
The module reads roles directly from wp_roles(), never redefining or overriding what a role actually is.
Built directly around WordPress's own notice hooks
The supplied code integrates through APIs present in WordPress core; this page makes no compatibility claim beyond the verified implementation.
admin_notices and all_admin_notices
The two native hooks WordPress core and virtually every plugin use to print a notice box at the top of an admin screen.
user_admin_notices and network_admin_notices
The native hooks used for user-profile and network-admin notices specifically in a WordPress multisite installation.
towp_user_roles filter respected
Role checks run through the same filter a Multi Role module can extend, so multi-role users get evaluated correctly.
TheOneWP versus common alternatives
Compare the verified implementation with an all-or-nothing notice-hiding snippet.
| Capability | TheOneWP Disable Admin Notifications by Role | Other common solutions |
|---|---|---|
| Choosing which roles go quiet | Any registered role, selected individually | Often all-or-nothing, affecting every logged-in user |
| Multisite notice coverage | Standard, network and user notices all included | Frequently limited to the single-site admin_notices hook |
| Performance when unused | No hook registered unless a role is selected | Some approaches always run a check on every admin page load regardless |
| Administrator eligibility | Can be selected like any other role | Sometimes hardcoded to always show notices to administrators |
| Administration | One settings screen, checkboxes per role | Often requires a code snippet targeting specific plugin notices |
Quiet a role's dashboard in four steps
Confirm the change from an affected role's own login before considering it done.
Enable Disable Admin Notifications by Role
Activate the module from the TheOneWP Components settings tab.
Select the roles that should see a clean screen
Check the roles whose dashboard shouldn't be cluttered with plugin and system notices.
Log in as an affected role to confirm
Verify the admin screen renders without the usual notice boxes for a selected role.
Leave maintenance-focused roles unselected
Keep notices visible for whichever role actually acts on plugin updates and configuration messages.
Choose by responsibility, not by seniority
The right selection depends on who actually needs to see maintenance information, not on role hierarchy.
Select roles by responsibility, not by seniority
Base the choice on who actually maintains the site, not on which role happens to be more senior.
Leave at least one role able to see maintenance notices
Someone still needs to see plugin update and configuration messages, so make sure that role stays unselected.
Revisit the selection after adding a new role
A newly created role won't be selected automatically, so decide deliberately whether it should see notices or not.
Communicate the change to affected roles
A quieter dashboard is the intended outcome, but it's worth letting affected users know notices were disabled on purpose.
Avoid silencing the role that actually needs to hear it
A couple of details are easy to overlook when selecting roles for the first time.
Selecting every role, including the one that maintains the site
If no role is left able to see notices, plugin updates and configuration warnings can go unnoticed by everyone.
Assuming only the most common notice type gets removed
All four notice hooks get removed together for a selected role; there's no way to keep one type visible while removing another.
Forgetting a custom role needs its own selection
A custom role doesn't inherit the setting from a similar built-in role; it needs to be checked separately.
Disable Admin Notifications by Role FAQ
These answers come directly from the verified class and its settings registration.
What does Disable Admin Notifications by Role do?
It removes the colored notice boxes WordPress and its plugins show at the top of admin screens, for whichever roles get selected in the settings.
Which notices actually get removed?
Standard admin notices, notices shown on every admin page, and the multisite-specific user and network admin notices, all four together.
Can I disable notices for Administrator?
Yes. Administrator can be selected exactly like any other role; nothing is automatically exempt.
Does this remove notices selectively, keeping some visible?
No. Once a role is selected, every notice gets removed for that role; there's no per-plugin exception.
Does this work with custom roles, not just WordPress's default ones?
Yes. The role list comes from every role actually registered on the site, including custom ones.
Will a role I don't select notice any change at all?
No. Notices continue to appear exactly as before for any role that isn't selected.
Does this affect performance on a site that doesn't use the feature?
No. The module doesn't register its notice-removal hook at all unless at least one role has been selected.
Does this hide anything from the front end of the site?
No. The module only affects notices shown inside wp-admin, not anything visitors see on the site itself.
Will this work correctly for a user with more than one role?
Yes. Role matching checks every role a user has, so notices get removed if any of their roles is selected.
Who can choose which roles have notifications disabled?
Only an administrator with access to the TheOneWP settings screen.
Stop showing every role the same wall of notices.Give the roles that don't need them a clean screen.
Use Disable Admin Notifications by Role to silence plugin and system notices for chosen roles, while keeping them fully visible for whoever actually needs to act on them.