BuddyBoss Notifications: Complete Setup & Config Guide
BuddyBoss runs four distinct notification channels: on-screen (bell icon), email, web push via OneSignal, and mobile app push via Firebase. Each channel has its own setup requirements, and getting all four working correctly is what separates a community that members actually engage with from one they quietly ignore.
Most guides cover one channel at a time, leaving you to stitch together six different documentation pages to get the full picture. We’ve built BuddyBoss-powered communities across course platforms, membership sites, and social networks, and we’ve hit every configuration pitfall in this guide at least once.
What follows is the complete, unified setup reference we wish had existed when we started. We cover prerequisites, step-by-step configuration for each channel, email deliverability, troubleshooting the most common bugs, and a practical framework for choosing the right channel for each use case.
Explore BuddyBoss and Get Started
What Is the BuddyBoss Notification Architecture?
BuddyBoss splits notifications across four channels, and they are genuinely separate systems with different triggers, different infrastructure, and different admin controls. Understanding the architecture before touching any settings saves a lot of debugging time later.
On-screen notifications appear inside your site via the bell icon in the navigation bar. Email notifications go to members’ inboxes through your WordPress mail system. Web push notifications arrive in the browser or desktop OS even when the member has your site closed. Mobile app push notifications fire through the BuddyBoss App via Google Firebase, reaching members on their phones regardless of what they are doing.
Which Plugins and Licenses Do You Actually Need?
This is the question that trips up most new admins. Not every channel is available on every plan.
| Notification Channel | Required Plugin | License Required | Third-Party Service |
|---|---|---|---|
| On-Screen (Bell) | BuddyBoss Platform | Free | None |
| Email Notifications | BuddyBoss Platform | Free | SMTP service recommended |
| Web Push (Browser) | BuddyBoss Platform Pro | Platform Pro required | OneSignal (free tier available) |
| Mobile App Push | BuddyBoss App plugin | BuddyBoss App license | Google Firebase (free tier available) |
Web push is gated behind Platform Pro, so if you are on the free Platform only, you will not see the OneSignal settings. Mobile app push requires the separate BuddyBoss App plugin, which is a distinct purchase from the Platform and Platform Pro licenses.
How Do You Set Up On-Screen Notifications?
On-screen notifications are the simplest channel to configure. Go to BuddyBoss > Settings > Notifications and you will find the on-screen controls under the “On-Screen Notifications” tab.
You can set the auto-hide timer (how many seconds the popup stays visible), toggle the browser tab badge (the number that appears on the favicon in the browser tab), and control whether the notification bell appears on mobile. These are all site-wide defaults.
One thing to know upfront: on-screen notifications poll for updates on a 30-second cycle. BuddyBoss does not use WebSockets for real-time delivery, so there is an inherent delay before a new notification appears. This is not a bug and there is no current workaround in the core platform. If a member asks why their notification appeared late, this is why.
How Do You Configure Email Notifications?
Email notifications are controlled from two places: the global Notification Types panel and the individual email templates.
Navigate to BuddyBoss > Notifications to reach the Notification Types panel. Each notification type (friend request accepted, new group member, course progress, etc.) has toggles for Email, Web, and App channels. You can enable or disable each channel per notification type from this single screen, which is far more efficient than hunting through component settings.
How Do You Customize Email Notification Templates?
Click the edit icon on any notification type row and you can modify the email subject and body. Templates support merge tags like {{{member.name}}}, {{{site.name}}}, and activity-specific tags that vary by notification type. The available tags for each template are listed in the editor sidebar.
Keep customizations minimal at first. Heavily modified templates can break if you run the Repair Community tool later, because it restores templates to defaults. Test your custom templates by triggering the relevant action on a staging account before going live.
How Do You Fix Missing Email Templates with Repair Community?
After a major plugin update, some email templates occasionally go missing from the Notification Types panel. The fix is straightforward: go to BuddyBoss > Tools > Repair Community and run the “Reinstall default notification emails” repair. This restores any missing templates from the plugin defaults.
Be aware this also resets any custom template edits you have made. Document your customizations before running Repair Community, or you will need to reapply them afterward.
Can Members Control Which Notifications They Receive?
Yes. Members can manage their own notification preferences from their profile settings at Profile > Settings > Notifications. They see the same channel toggles (Email, Web, App) per notification type that admins see in the backend, but only for the types the admin has enabled globally. If an admin turns off email for a notification type site-wide, members cannot re-enable it.
Email Deliverability: The Step Most Admins Skip
WordPress sends email through PHP’s mail() function by default. Most shared hosting environments either block it outright or deliver it so unreliably that notifications end up in spam. This is the most common reason members report not receiving BuddyBoss email notifications.
The fix is to route all outgoing WordPress mail through a dedicated SMTP service. Install a plugin like WP Mail SMTP, then connect it to a transactional email provider such as SendGrid, Mailgun, or Postmark. All of these have free tiers sufficient for small communities.
After connecting your SMTP provider, configure SPF and DKIM records in your domain’s DNS. Your email provider will give you the exact record values.
SPF tells receiving mail servers that your provider is authorized to send on your domain’s behalf. DKIM adds a cryptographic signature that proves the email was not tampered with in transit. Both are required to pass spam filters reliably in 2026.
Use the “Send Test Email” feature inside WP Mail SMTP to confirm delivery before assuming it works. Then send yourself a test notification from BuddyBoss itself (trigger a friend request or group invitation) and verify the email arrives in the inbox, not spam.
How Do You Delay Message Email Notifications in BuddyBoss?
Direct message notifications have a separate delay control. Go to BuddyBoss > Settings > Notifications > Messaging and you will find a dropdown to delay message email digests anywhere from 15 minutes to 24 hours. You can also hide new message notifications from the bell icon entirely here if you want messages to live only in the inbox.
The delay makes sense for active communities where members exchange multiple messages in quick succession. Without it, a 10-message conversation generates 10 separate email notifications. Setting a 15-30 minute delay collapses those into one digest, which is a significant quality-of-life improvement for your members.
How Do You Connect BuddyBoss to OneSignal for Web Push?
Web push requires Platform Pro. Once you have that active, go to BuddyBoss > Settings > Notifications > Web Push.
First, create a free account at OneSignal.com and create a new app. Select “Web” as the platform. OneSignal will generate an App ID and a REST API Key. Paste both into the corresponding fields in BuddyBoss settings.
The “Soft Prompt” setting is worth enabling. Instead of the browser’s native permission prompt (which many members dismiss reflexively), a soft prompt shows a custom in-page banner first, explaining why they should allow notifications. This consistently produces better opt-in rates than jumping straight to the native browser dialog.
The “Skip Active Members” setting controls whether push notifications fire for members who are currently active on your site. Enabling it prevents a member who is already browsing your community from also receiving a push notification about activity they are likely already seeing. We recommend enabling this.
For notification icons, OneSignal requires a square image of at least 192×192 pixels. The icon must be served over HTTPS. A mismatch here (HTTP icon URL on an HTTPS site) causes the notification to appear without an icon, which looks unprofessional and reduces click rates.
How Do You Set Up Firebase for BuddyBoss App Push Notifications?
Mobile push for the BuddyBoss App runs through Google Firebase. This setup has more steps than OneSignal, and it requires access to both the Google Firebase console and your BuddyBoss App plugin settings.
Create a new project at console.firebase.google.com. Inside the project, add an Android app and an iOS app using your app’s bundle ID.
Firebase will generate a google-services.json file for Android and a GoogleService-Info.plist file for iOS. Download both.
In your WordPress admin, go to BuddyBoss App > Components > Push Notifications. Upload the JSON file for Android and the Plist file for iOS into the corresponding fields. Save settings.
What About the Firebase V1 API Migration?
Google deprecated the legacy Firebase Cloud Messaging (FCM) API and has been migrating services to the FCM V1 API. If your BuddyBoss App was set up before this migration window, your push notifications may silently stop working without any obvious error in the dashboard.
To migrate, generate a new service account private key from the Firebase console under Project Settings > Service Accounts > Generate new private key.
The BuddyBoss App plugin settings have a field specifically for the V1 API credentials. Upload the JSON key file there instead of the old server key. If you are unsure which API version you are using, check BuddyBoss App > Push Notifications and look for which credential fields are populated.
Automated vs. Manual Push Notifications
Automated push notifications fire based on community activity: new posts, course completions, group invites, and so on. These are configured by enabling the relevant notification types in the Notification Types panel.
Manual push lets you broadcast a custom message to a segmented audience. In BuddyBoss App > Push Notifications > Send Notification, you can write a custom message and target it by group membership, course enrollment, or BuddyBoss membership level. You can also add a deep link so tapping the notification opens a specific page inside the app rather than the app home screen.
What Is the Difference Between On-Screen and Web Push Notifications?
On-screen notifications only appear when a member is actively on your site. They show up in the bell icon dropdown and as temporary popup banners in the corner of the browser window. When the member leaves your site, on-screen notifications stop.
Web push notifications arrive via the browser’s native notification system, which runs independently of your site. A member can have your site completely closed and still receive a web push notification on their desktop or laptop. This is the key functional difference, and it is why web push drives significantly better re-engagement for inactive members.
Troubleshooting the Most Common BuddyBoss Notification Problems
Why Is the Notification Bell Showing Unread Notifications with an Empty Inbox?
This is a known bug in BuddyBoss where the notification counter becomes out of sync with actual unread items. It typically happens after bulk activity (importing content, running repairs) or after a notification type gets disabled while members have unread notifications pending.
The workaround is to go to BuddyBoss > Tools > Repair Community and look for a repair option related to notification counts. This resyncs the counters. If the problem recurs after specific actions, note what triggers it and report it to BuddyBoss support with those reproduction steps.
Why Aren’t Forum Subscription Notifications Working?
Forum subscription notifications are one of the more fragile parts of the system. The most common cause is that the member’s email subscription preference for the forum is set to “No Email” in their profile. Check Profile > Settings > Notifications on the affected member’s account.
If the preference looks correct, the next suspect is SMTP delivery failure. Run a test email from WP Mail SMTP to confirm emails are routing properly. The third cause is a missing or corrupted email template for forum subscriptions: run Repair Community to restore it.
Why Are Push Notification Links Opening in the Browser Instead of the App?
This happens when deep links are not configured correctly in the BuddyBoss App settings, or when the notification was sent with a standard HTTPS URL rather than a deep link scheme. Review your app’s URL scheme settings and ensure manual push notifications use the app’s deep link format rather than plain web URLs.
Notification Strategy: Choosing the Right Channel for the Right Use Case
Running all four channels at maximum volume is a fast way to train your members to ignore everything you send. Channel selection by intent is the solution.
Use email for transactional notifications where the member genuinely needs a record: payment confirmations, course enrollments, password resets, and detailed activity digests. Email is the right choice when the content benefits from being saved and referenced later.
Use web push for time-sensitive re-engagement: a live event starting, a limited-time offer, or a reply to a discussion the member participated in. Push gets attention when the member is not on your site, which is exactly when re-engagement matters most.
Use on-screen notifications for ambient social activity: friend requests, reactions, and group activity that members will see naturally the next time they visit. These do not need to interrupt anyone.
Use mobile app push for your most engaged members who have downloaded the app. This audience self-selects as high-intent, so slightly higher frequency is acceptable here without the same fatigue risk.
On frequency: a digest model for email (grouping multiple notifications into one message) almost always outperforms sending every event individually. For push, stay conservative. One to three pushes per week per member is a reasonable ceiling for most community types. Trigger push around milestone events rather than every small activity update.
GDPR and CCPA compliance matters for web and mobile push specifically. Both channels require affirmative opt-in before you can send. OneSignal’s soft prompt handles this for web push. For mobile, the iOS App Tracking Transparency framework requires explicit permission. Document your opt-in mechanism and store consent records.
If you are still evaluating whether BuddyBoss is the right platform for your community, our BuddyBoss vs. Mighty Networks comparison covers how the two platforms stack up across features, pricing, and notification capabilities. And if you are running an LMS alongside your community, the Best WordPress LMS Plugins guide gives full context on how BuddyBoss integrates with LearnDash and other course tools.
Why This Matters Right Now
For BuddyBoss communities, the four-channel architecture gives operators more control than most competing platforms, but only if those channels are properly configured. A misconfigured Firebase credential or missing SMTP setup can silently undermine an otherwise well-built community without any obvious error message pointing to the cause.
Frequently Asked Questions
Do I need BuddyBoss Platform Pro to use web push notifications?
Yes. Web push via OneSignal requires an active BuddyBoss Platform Pro license. The OneSignal settings tab will not appear in your admin if you are running the free Platform only.
Why are my BuddyBoss email notifications not being sent?
The most common causes are WordPress sending mail through PHP’s unreliable default system, a missing or corrupted email template, or the notification type being disabled for the Email channel. Install WP Mail SMTP with a transactional provider, run Repair Community to restore templates, and confirm the notification type has Email toggled on in the Notification Types panel.
Why do BuddyBoss on-screen notifications take 30 seconds to appear?
BuddyBoss uses a polling mechanism that checks for new notifications every 30 seconds rather than a real-time WebSocket connection. This is a platform-level architectural choice, not a configuration error, and there is no native setting to reduce the interval.
How do I migrate from Firebase legacy Cloud Messaging to Firebase V1 API?
Generate a new service account private key from Firebase console under Project Settings > Service Accounts, then upload that JSON key file in BuddyBoss App > Push Notifications using the V1 API credentials field. Remove the old legacy server key once the new credentials are confirmed working.
Why aren’t my forum subscription notifications working in BuddyBoss?
Check three things in order: the affected member’s notification preference for forum subscriptions in their profile settings, your SMTP delivery configuration (use WP Mail SMTP’s test email to confirm), and whether the forum email template exists (run Repair Community if it is missing).
How do I stop BuddyBoss from sending too many notification emails to members?
Use the Notification Types panel to disable Email for low-priority notification types, enable message email digests with a delay (15 minutes to 24 hours), and communicate to members that they can self-manage preferences from their profile settings. A digest strategy for message notifications alone typically cuts email volume significantly.
Why is my BuddyBoss notification bell showing unread notifications but the inbox is empty?
This is a counter sync bug. Go to BuddyBoss > Tools > Repair Community and look for a repair option related to notification counts to reset the counters to match actual unread items.
Getting Your Notifications Right Is Worth the Setup Time
The four-channel notification system in BuddyBoss is genuinely powerful once all the pieces are in place. On-screen handles ambient social activity, email handles transactional records, web push re-engages members who have left, and mobile app push reaches your most committed audience wherever they are.
The setup is not trivial, especially the SMTP deliverability work and Firebase V1 migration for existing app users. But every hour you invest in getting this right pays back in the form of members who stay connected, return more often, and are far less likely to churn.
