# Preventing/Limiting Group Message Archiving **URL:** \ **Category:** Product Support\ **Created:** [January 29, 2020, 4:51am UTC](https://meta.discourse.org/t/preventing-limiting-group-message-archiving/140016 "2020-01-29T04:51:25Z")\ **Posts on this page:** 1\ **Showing post:** 3
**Author:** ![justin](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/justin/32/157614_2.png) [@justin](https://meta.discourse.org/u/justin)\ **Post date:** [January 29, 2020, 11:53am UTC](https://meta.discourse.org/t/preventing-limiting-group-message-archiving/140016/3 "2020-01-29T11:53:50Z")
> [@reoguy55](#): > > For clarification, we think that staff members are archiving the message after viewing/responding, but we would rather keep the message thread open so the other 100+ staff members can still see the thread. This sounds like more of a need to adhere to a process for handling these messages than a need for a new feature. We use group inboxes here to handle support for our hosting customers and we archive when a message has been handled. That message will pop back into the inbox of there’s another reply, though. I have a few thoughts that might help — - archived messages will still show as unread for any user who has not read them. A possible workflow is to have users browse the archive for unread messages. - some of us here want to keep up on all the message history, and one way we do that is through setting the group inbox to Watching. This will notify you of every message added to those topics. Then each user can use their notifications tab in their user profile to catch up on unread topics. You could also explore using a private category as well like @tobiaseigen suggested. Hope that helps! --- _[View the full topic](https://meta.discourse.org/t/preventing-limiting-group-message-archiving/140016)._