# Mark notification as read

**URL:** <https://forum.heroiclabs.com/t/mark-notification-as-read/5216>\
**Category:** Runtime Framework\
**Tags:** server-framework\
**Created:** [April 29, 2024, 3:32pm UTC](https://forum.heroiclabs.com/t/mark-notification-as-read/5216 "2024-04-29T15:32:03Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![elementalcode](https://sea2.discourse-cdn.com/flex020/user_avatar/forum.heroiclabs.com/elementalcode/32/1697_2.png) [@elementalcode](https://forum.heroiclabs.com/u/elementalcode)\
**Post date:** [April 29, 2024, 3:32pm UTC](https://forum.heroiclabs.com/t/mark-notification-as-read/5216/1 "2024-04-29T15:32:03Z")

</div>

The only way I see to implement a system to “mark as read” or “mark as unread” for notifications would be to use the storage service to store a set (list, array, etc) of read/unread notification ids.

**currently notifications cannot be edited, not even serverside, right?** deleting the notification and re-adding it with a `read:true` in the content seems a bit counterproductive since my cursor and ordering would fly out the window 😢

Edit:  
Just to hack stuff… if I were to tamper with the database similar to [nakama/server/core\_notification.go at e3f170cd081b18338cc863f1f86b8ea795d36939 · heroiclabs/nakama · GitHub](https://github.com/heroiclabs/nakama/blob/e3f170cd081b18338cc863f1f86b8ea795d36939/server/core_notification.go#L289) but with an update command… could it work? (I know this is not the expected way of doing stuff, but it _could_ work 👀 )

---

<div class="post-metadata">

**Author:** ![sesposito](https://sea2.discourse-cdn.com/flex020/user_avatar/forum.heroiclabs.com/sesposito/32/2594_2.png) [@sesposito](https://forum.heroiclabs.com/u/sesposito)\
**Post date:** [May 2, 2024, 11:23am UTC](https://forum.heroiclabs.com/t/mark-notification-as-read/5216/2 "2024-05-02T11:23:39Z")

</div>

Hello @elementalcode,

Since we don’t currently provide an API to update a notification content, a custom query is fine for this purpose, I’d suggest using something like:

```sql
UPDATE notification SET content = content || '{"read":true}'::jsonb WHERE id = '<notification_id>';

```

Best