# \[DONE\] Turn "Notifications" into "Inbox"

**URL:** <https://community.fibery.io/t/done-turn-notifications-into-inbox/2251>\
**Category:** Ideas & Features\
**Tags:** notifications\
**Created:** [November 24, 2021, 12:15pm UTC](https://community.fibery.io/t/done-turn-notifications-into-inbox/2251 "2021-11-24T12:15:58Z")\
**Posts on this page:** 1\
**Showing post:** 5

<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:** [December 24, 2021, 6:06pm UTC](https://community.fibery.io/t/done-turn-notifications-into-inbox/2251/5 "2021-12-24T18:06:30Z")

</div>

@mdubakov I wanted to respond to your message over here:

> [@Search in Notifications](https://community.fibery.io/t/search-in-notifications/2330/4):
>
> Notifications are just messages, not data, so we will not implement search in notifications. However, we will make them work eventually. This is not a top priority for us, we are focusing on Blocks and Permissions.

Since you closed that thread, I’m adding in my additional context in this thread.

I would like to ask that you to consider that over time, the activity users can generate in ranges of @mentions among other teammates does indeed constitute very relevant content that has a category of its own. I’d draw a similarity to Slack, which tons of teams use exclusively for messaging each other, making simple requests of a “to do” nature, etc. Slack has leveraged exceptional search functionality as one if its big selling points, and I think that they are right. Teams have a need to index and search their history of notifying each other outside other tools that are more “robust” that they use to compliment Slack, such as Work Management apps like Fibery.

In an initial run in Fibery, when a team is getting started and perhaps not using Fibery for all-out management of its work, then initially I agree notifications can seem to be not that relevant content. But when you are using Fibery actively day-in, day-out, as we have been doing, for a long time, what gets generated within notifications is a type of content that is worth its own very relevant “citizenship” in Fibery I would argue.

And, since Notifications are basically just comments with the addition of an @mention which makes them show up in the Notifications Pane, I hope you guys will consider this request still:

> [@Refer to Comments, and Public ID’s for Comments](https://community.fibery.io/t/refer-to-comments-and-public-id-s-for-comments/1251):
>
> Hi guys, I wanted to add another request around Comments: As I have discussed around here, my team heavily relies on Comments in Fibery. Often in light of the great linking around Fibery, I find myself instinctively trying to link to a comment. So I wanted to request that Comments be surfaced as “referable items” like Docs and Views, alongside Entities. I’d also like to add that it would be very useful if each Comment had its own visible Public ID. Some tools such as [Clubhouse.io](http://Clubhouse.io) have that …

Ideally though, it would be great to be able to isolate the @mentions out of comments into a separate group of content that could be viewed on its own - in other words, “Notifications.” If ultimately you could search through only comments with a filter for @mentions, you would accomplish this as well.

Thanks for your consideration!

---

_[View the full topic](https://community.fibery.io/t/done-turn-notifications-into-inbox/2251)._