Community Notifications
Community notifications keep publishers and users informed about activity that matters to them — new replies to threads they're watching, @mentions, accepted-answer events, and package announcements. Notification preferences are fully configurable per user.
Notification Triggers
| Event | Who Is Notified | Delivery Speed |
|---|---|---|
| New reply to a thread you started | Thread author | Real-time |
| New reply to a thread you replied to (if subscribed) | Subscriber | Real-time |
| @mention in a post | Mentioned user | Immediate |
| Your reply marked as accepted answer | Reply author (the one who answered) | Real-time |
| New announcement in a package you follow | Package followers and installed-package tenants (for security advisories) | Real-time |
| New thread in a package forum you follow | Package followers | Batched (hourly digest option) |
| Reply to your reported content (resolution notice) | Reporter | Real-time |
| Moderation action on your account | Moderated user | Immediate |
Subscription Types
Thread Subscriptions
Subscribe to any specific thread to receive notifications when new replies are posted. Thread authors are auto-subscribed to their own threads. You can unsubscribe from any thread at any time.
Package Forum Subscriptions
Subscribe to a package's forum to receive notifications about new threads and announcements in that package's community. Users who install a package are not auto-subscribed — subscription is always opt-in.
@Mention Notifications
@mention notifications are always on and cannot be disabled — this ensures mentions are always seen. If a user is banned from posting, they still receive @mention notifications (read access is retained).
Announcement Notifications
Security advisory announcements are sent to all tenants with the affected package installed, regardless of subscription status. Standard package announcements go only to forum subscribers.
Notification Delivery Channels
| Channel | Available For | Configurable? |
|---|---|---|
| In-platform notification bell | All notification types | Always on; cannot be disabled |
| Email (immediate) | @mentions, accepted answer, moderation actions, security advisories | Can disable per notification type in account settings |
| Email (hourly digest) | Thread replies, new forum threads | Can switch between immediate and digest per notification type |
| Email (daily digest) | Thread replies, new forum threads | Alternative to hourly digest |
Publisher Notification Defaults
Publisher accounts have different default notification settings than tenant accounts, because publishers need to be responsive to their package communities:
- New questions tagged with publisher's packages: Email immediate (default ON)
- New replies to publisher's own threads: Email immediate (default ON)
- Accepted answer on publisher's replies: Email immediate (default ON)
- New threads in publisher's package forums: Email daily digest (default ON)
- All other community activity: In-platform only (default; email opt-in)
Managing Notification Preferences
All notification settings are managed from Account Settings → Notifications. Settings can be adjusted per notification type and per delivery channel independently. Publishers can also set notification preferences per package in the Publisher Dashboard → Community tab, which overrides account-level defaults for that specific package.
The notification bell in the platform header shows an unread count badge. Clicking the bell opens a notification panel showing the last 50 notifications with read/unread status. Marking all as read clears the badge. Notifications older than 90 days are archived and accessible from Account Settings → Notification History.