Feature Request: In-App Notification Center #5551

New Issue

OVERLORD · 2026-02-05T10:10:02+03:00

OVERLORD commented

2026-02-05 10:10:02 +03:00

Originally created by @AryeComb on GitHub (Dec 23, 2025).

Describe the feature you'd like

Current Behavior:

Notifications (page updates, comments, mentions) are only sent via email. Users must check their email to see activity.

Proposed Feature:

Add an in-app notification center with:

Bell icon in header showing unread count
Dropdown list of recent notifications
Mark as read/unread functionality
Link directly to relevant content

Describe the benefits this would bring to existing BookStack users

Reduces email fatigue for active users
Immediate visibility of activity without leaving BookStack
Better user experience for teams collaborating in real-time
Complements (doesn't replace) existing email notifications

Can the goal of this request already be achieved via other means?

Partially, with significant limitations:

The theme system (logical + visual) could theoretically query mention_history table and display a basic list
However, this only covers mentions (not other notification types) and has no read/unread tracking
Would require custom database tables/logic which goes beyond theme system capabilities
A proper implementation requires core changes to notification storage and API endpoints

** Disclaimer ** This section was made with an AI, I didn't validate his thinking and didn't try to implement that myself

Have you searched for an existing open/closed issue?

I have searched for existing issues and none cover my fundamental request

How long have you been using BookStack?

Under 3 months

Additional context

No response

Originally created by @AryeComb on GitHub (Dec 23, 2025). ### Describe the feature you'd like ### Current Behavior: Notifications (page updates, comments, mentions) are only sent via email. Users must check their email to see activity. ### Proposed Feature: Add an in-app notification center with: - Bell icon in header showing unread count - Dropdown list of recent notifications - Mark as read/unread functionality - Link directly to relevant content ### Describe the benefits this would bring to existing BookStack users - Reduces email fatigue for active users - Immediate visibility of activity without leaving BookStack - Better user experience for teams collaborating in real-time - Complements (doesn't replace) existing email notifications ### Can the goal of this request already be achieved via other means? Partially, with significant limitations: - The theme system (logical + visual) could theoretically query mention_history table and display a basic list - However, this only covers mentions (not other notification types) and has no read/unread tracking - Would require custom database tables/logic which goes beyond theme system capabilities - A proper implementation requires core changes to notification storage and API endpoints ** Disclaimer ** This section was made with an AI, I didn't validate his thinking and didn't try to implement that myself ### Have you searched for an existing open/closed issue? - [x] I have searched for existing issues and none cover my fundamental request ### How long have you been using BookStack? Under 3 months ### Additional context _No response_

OVERLORD added the 🔨 Feature Request label 2026-02-05 10:10:02 +03:00

OVERLORD commented

2026-02-05 10:10:04 +03:00

@AryeComb commented on GitHub (Jan 8, 2026):

@ssddanbrown hi, sorry to nag you, but can you give some input about it? E.g. do you think it's a good idea? Would you consider putting it on the roadmap? Are you open for code contribution?

@AryeComb commented on GitHub (Jan 8, 2026): @ssddanbrown hi, sorry to nag you, but can you give some input about it? E.g. do you think it's a good idea? Would you consider putting it on the roadmap? Are you open for code contribution?

OVERLORD commented

2026-02-05 10:10:04 +03:00

@ssddanbrown commented on GitHub (Jan 8, 2026):

@AryeComb I think it's a reasonable idea, but I think there'd be some complexity when it comes to implementing it in a way that's actually useful to users instead of burdensome, and in a way that works alongside email notifications.

It would increase the scope of this area a fair bit, and therefore I don't think it'd be worthwhile to add at this time, since there has not been proven need or demand. Therefore I wouldn't plan to work on it nor accept a PR at this time.
I expect the need/desire may grow though as we add more notification/email-emitting features.

@ssddanbrown commented on GitHub (Jan 8, 2026): @AryeComb I think it's a reasonable idea, but I think there'd be some complexity when it comes to implementing it in a way that's actually useful to users instead of burdensome, and in a way that works alongside email notifications. It would increase the scope of this area a fair bit, and therefore I don't think it'd be worthwhile to add at this time, since there has not been proven need or demand. Therefore I wouldn't plan to work on it nor accept a PR at this time. I expect the need/desire may grow though as we add more notification/email-emitting features.

Sign in to join this conversation.

Branches Tags

1 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: starred/BookStack#5551