WordPress plugins could soon have to declare why they send notifications and where those messages appear. A proposal posted to Make WordPress Core on November 16 describes a channel-based system for classifying notices, restricting promotional banners, and checking plugin behavior.
This WordPress notification proposal is still under discussion, not an adopted WordPress feature. Plugin developers can use this report to understand the suggested intent categories, how checks might work, and which parts still need feedback.
What the WordPress notification proposal would change
The proposal responds to a specific concern: promotional notices from directory plugins can fill the WordPress admin dashboard. Its author, Jonathan Bossenger, suggests making plugins declare the intent behind each notification channel so tools can check whether notices follow the rules.
In the proposed model, an admin notice is another place a channel can display a message, rather than a separate notification system. WordPress Core notices would be exempt at first; plugins would need to declare intent. The proposal aims to reuse work from the WP Feature Notifications project while focusing on intent declarations and enforcement. Read the full proposal and its implementation details.
Five intents would classify plugin messages
Each channel would have one intent, registered in advance so tools can read it without running the plugin. The draft proposes five categories: operational, setup, activity, feedback, and promotional. The distinction is about why a notification appears, not how urgent it is.
operationalcovers a change to the site or an automated process, or an issue that needs attention, such as a failed backup or an available update.setupcovers an unfinished task, such as connecting an account, and should stop once the task is complete.activitycovers an action by another person or agent that involves the user, such as a new comment or mention.feedbackreports the result of the user’s own action, such as a saved setting or invalid email address.promotionalcovers messages initiated by the sender, including upsells, discounts, tips, review requests, and surveys.
The examples make clear why the proposal separates intent from message wording. A notice that a license has expired and updates have stopped is operational because it reports a change in site state. A message asking someone to renew before their license expires is promotional because it asks for payment ahead of time.
Where each notice could appear
The draft pairs intent with rules for the notification centre, admin notices, and severity. Operational messages could appear in both the centre and admin notices. Setup notices could also use both, but admin notices would need to be dismissible. Activity would go to the centre rather than admin notices, while feedback would appear only after the user’s action and would not be stored in the centre.
Promotional messages could appear in the centre, but their admin notices would be hidden on a fixed list of Core screens and would need to be dismissible. Their severity would be limited to info, or left unset. The draft says a security alert would remain operational, with alert severity, rather than being treated as a separate intent.
The author does not propose checking whether a notice appears only on a plugin’s own screens. The proposal says WordPress cannot reliably identify which plugin added a menu page at runtime. Instead, promotional notices would be hidden on selected Core screens, such as Dashboard, Plugins, Posts, and Settings. A later system could let channels declare screens and let Plugin Check compare them with a plugin’s registered menu pages.
How the proposed checks would work
The draft says the first version could pass a channel name through the existing wp_admin_notice() helper. The current argument handling would preserve that unknown key, allowing the feature plugin to use existing filters to look up the channel’s intent, enforce rules, or hide a notice that breaks them. On sites without the feature plugin, the channel key would be ignored.
That means developers could try adding channels before Core has a corresponding update, according to the proposal. Later Core work would add a channel registry and document a prefixed registration function. The proposed channels would also provide a plugin namespace, plus a basis for persistent dismissals and per-user muting.
Enforcement has two tracks. Plugin guidelines could be updated first, with human review checking intent rules. The feature plugin would test the registry, runtime behavior, and dismissals; Plugin Check could then flag issues such as missing channels or promotional channels using a disallowed severity.
The proposal also draws a boundary around undeclared notices. The feature plugin would not hide every notice without a channel at runtime, because it may not be able to distinguish a Core notice from a plugin notice reliably. Static checks and directory review would handle plugin cases instead.
What developers should watch next
This is a proposal, so the categories, exceptions, and enforcement plan can still change. Comments on the post question whether five intents are too many, whether activity messages sometimes need to appear beside the screen they describe, and whether Plugin Check should begin with warnings before turning them into errors.
The author asks for feedback by Monday, November 30, 2026. Plugin developers who rely on admin notices should review the proposed categories and add a comment before that deadline, especially if a notice does not fit the examples or rules in the draft.
FAQ
Has WordPress adopted these notification rules?
No. The November 16 post presents a proposal for discussion. It describes possible guidelines, feature-plugin work, and later Core changes rather than a released WordPress feature.
Would Core notices need to declare an intent?
Not in the proposal’s first version. It exempts Core’s own admin notices and places the declaration requirement on plugins. The post says Core could adopt channels later.
When is feedback due?
The proposal requests comments by Monday, November 30, 2026. Developers and site owners can leave feedback on the Make WordPress Core post.