# \[FIXED\] @mention in comments creating two notifications

**URL:** <https://community.fibery.io/t/fixed-mention-in-comments-creating-two-notifications/1554>\
**Category:** Bugs & Issues\
**Created:** [April 12, 2021, 10:12pm UTC](https://community.fibery.io/t/fixed-mention-in-comments-creating-two-notifications/1554 "2021-04-12T22:12:56Z")\
**Posts on this page:** 1\
**Showing post:** 3

<div class="post-metadata">

**Author:** ![colman](https://avatars.discourse-cdn.com/v4/letter/c/b9e5f3/32.png) [@colman](https://community.fibery.io/u/colman)\
**Post date:** [June 22, 2021, 5:14pm UTC](https://community.fibery.io/t/fixed-mention-in-comments-creating-two-notifications/1554/3 "2021-06-22T17:14:32Z")

</div>

Yes, we don’t enjoy this!

I think this situation may be made worse by the fact that there aren’t ways to opt-in to all notifications, for example:

> [@\[DONE\] "Watcher" of an Entity](https://community.fibery.io/t/done-watcher-of-an-entity/563/6):
>
> Further, I’d like to be able to opt into notifications for an entire type or even a whole app. This would be especially useful if combined with granularity: e.g. receive all notifications from comments from this type (or app) would be my number one desire here

Because of this, we end up using @ notifications more than we otherwise would “just in case” (so we aren’t trying to remember who will or won’t be notified).

I think in terms of on-boarding, the two big remaining pain-points are the overall complexity of Fibery (which the Fibery team is aware of and working hard on, and to be fair is also to a degree simply part of the value prop of the product), and notifications. At least these are the two I feel the most right now! Notifications, in minor contrast to the complexity, I think can be improved without sacrificing value prop. And lastly, the complexity can be learned / gotten over, unlike most notification issues.

---

_[View the full topic](https://community.fibery.io/t/fixed-mention-in-comments-creating-two-notifications/1554)._