# Small element of Notifications - “I’ve read it” functionality

**URL:** <https://community.fibery.io/t/small-element-of-notifications-i-ve-read-it-functionality/1179>\
**Category:** Ideas & Features\
**Tags:** notifications\
**Created:** [November 17, 2020, 2:56pm UTC](https://community.fibery.io/t/small-element-of-notifications-i-ve-read-it-functionality/1179 "2020-11-17T14:56:41Z")\
**Posts on this page:** 1\
**Showing post:** 14

<div class="post-metadata">

**Author:** ![B\_Sp](https://avatars.discourse-cdn.com/v4/letter/b/e8c25b/32.png) [@B\_Sp](https://community.fibery.io/u/B_Sp)\
**Post date:** [January 30, 2023, 4:38pm UTC](https://community.fibery.io/t/small-element-of-notifications-i-ve-read-it-functionality/1179/14 "2023-01-30T16:38:20Z")

</div>

Great, so good to get the support of a community vet on this one!

We have ongoing issues with this, having to force new developers we onboard into Fibery to “please respond to a comment with a comment of your own that you read the comment” which is very unnatural this day in age when people are used to being able to “heart” or “like” comments, or even text messages for that matter, as an acknowledgement of having read them.

@Oshyan 's comment here:

> [@\[DONE\] Seeing "Closed" Entities grayed out in Search Dialog](https://community.fibery.io/t/done-seeing-closed-entities-grayed-out-in-search-dialog/1298/14):
>
> I can’t imagine what it’s like for even moderate-sized dev teams, etc. who have potentially 100s of tasks/bugs/etc. per week/month.

also illustrates some of the simple fixes we could get to help with trying to manage development and communication inside Fibery.

Thanks again!

---

_[View the full topic](https://community.fibery.io/t/small-element-of-notifications-i-ve-read-it-functionality/1179)._
