NotifHub

One bell. Every module. All your Dolibarr alerts, unified.

Free for every dev — an infrastructure module that handles notification display for you.

Every third-party Dolibarr module that needs to alert a user today reinvents its own icon, its own badge, its own dropdown — via the printTopRightMenu hook, with no shared format. The result: a cluttered top-right menu, no unified counter, no consistent read/unread state across modules. NotifHub gives every module one place to speak, and gives users one place to listen — free, as infrastructure should be.

🔔 One bell, every source

A single notification bell in the top menu aggregates alerts from every module that adopts NotifHub — no more competing icons fighting for space in the top-right corner.

⚡ Optional real-time toast (Flash)

Beyond the dropdown, a producing module can request an instant toast via Dolibarr's native jNotify — auto-dismiss for routine alerts, sticky for critical ones. Always additive: the notification stays in the dropdown either way. Toggleable instance-wide by the admin.

🔗 Grouped read state

Consumer modules can tag notifications with a group_key (a conversation, a case, a document) and mark the whole group read in one call — no need to reinvent a "mark all read" per business concept.

Key features

• ✅ Unified bell + unread badge counter in the Dolibarr top menu
• ✅ Dropdown history — module icon, title, short message, relative date
• ✅ Click a notification → mark read + redirect to the target URL supplied by the source module
• ✅ "Mark all as read" in one click
• ✅ Simple static PHP API for producer modules — NotifHubApi::push(), no UI to build
• ✅ Broadcast to all users or target a specific user
• ✅ Automatic purge of old read notifications via scheduled job (retention configurable)
• ✅ Configurable badge refresh interval (near real-time polling)
• ✅ Consistent rendering in both MD and Eldy themes — same bell, same alignment, same theme colors, out of the box

How it works

1. A third-party module calls NotifHubApi::push() when something worth surfacing happens (an incoming SMS, a completed workflow step...).
2. NotifHub stores the notification and updates the unread badge for the target user(s).
3. The user sees the badge, opens the bell, and reads the dropdown — grouped, timestamped, module-tagged.
4. A click marks it read and redirects to the source module's page. Optionally, an instant toast fires the moment it's pushed.

Support

NotifHub itself is free. Onboarding and custom integration support available at 90€/h. Custom development (new triggers, provider-style live notifications, additional targeting) on quote. Contact: products@dzprod.net

Changelog

1.0.0

• ✨ Initial release — bell, badge, dropdown, NotifHubApi::push(), read/unread, scheduled purge

1.1.0

• ✨ Configurable near-real-time badge refresh (NOTIFHUB_BADGE_POLL_INTERVAL)
• ✨ Grouped read state — group_key + markReadByGroup() (PHP and AJAX)

1.2.x

• ✨ Real-time toast notifications ("Flash") via native jNotify — auto-dismiss or sticky, opt-in per push, instance-wide admin toggle
• 🐛 Dropdown now lists unread only, with immediate removal on click (mobile-tray model)
• 🐛 Various hook context, install and alignment fixes

Questions or feature requests: products@dzprod.net — NotifHub is under active development.