Subscriber-group-specific notifications for private articles aren't working with new Athena

closed
· Articles & templates ·
By Those2Nerds on 01/13/2026
· Assigned to katerinach
· Waiting for Response

If your article is private, notifications should only be sent to members of assigned subscriber groups who have access to read the article. This works as expected in the old article edit interface. In the new article interface, notifications are sent to all followers regardless of their access to the notified article.   I tested this on a private world that only my test account follows. I published three private articles: one with no subscriber groups added, one with an empty subscriber group, and one with a subscriber group containing my test account.   When I sent notifications using new Athena, my test account should have only received one for the article it had access to, but instead received all three. Clicking the article links confirms the account does not have access to two of these articles.  

Steps to Reproduce

  1. Create and publish a private article.
  2. Assign a subscriber group.
  3. Using new Athena, send a notification to your followers.
  4. All followers will receive the notification, when only those who have access should.

Operating System

Windows

Browser

Other

History

mikolaszko @ 20 Jan, 2026 02:37:04 Developer
Assigned katerinach
katerinach @ 22 Jan, 2026 09:22:58 Assignee

Hey Those2Nerds, we have deployed a fix that should resolve this and send article notifications only to your subscriber group members if you set that article to private and have set subscriber groups! Please try again and let me know if this works as expected now.

katerinach @ 22 Jan, 2026 09:23:04 Assignee
katerinach Added tag Waiting for Response
Those2Nerds @ 22 Jan, 2026 05:19:49

I can confirm my test account only received a notification on the one article they had access to!   I also got an error when attempting to send a notification for a private article with no subscriber group, which is much appreciated! My one bit of feedback is that the error read "make sure your article is published", which it was. The actual problem was not having a subscriber group. If feasible, the cherry on top would be if the error could be more accurate to the problem.   Either way, this bug looks to be fixed and this can be closed. Thank you so much for resolving this so quickly!

katerinach @ 23 Jan, 2026 07:41:25 Assignee

Thanks for the response and I'll take a look to try and make the error a bit more accurate!

katerinach @ 23 Jan, 2026 07:41:29 Assignee
set this bug to closed