# Allow “Mark as Solution” in group messages

**URL:** https://meta.discourse.org/t/allow-mark-as-solution-in-group-messages/370496
**Category:** Feature
**Tags:** solved, completed
**Created:** [June 17, 2025, 9:47am UTC](https://meta.discourse.org/t/allow-mark-as-solution-in-group-messages/370496 "2025-06-17T09:47:56Z")
**Posts on this page:** 1
**Showing post:** 29

<div class="post-metadata">

### Author: ![zogstrip](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/zogstrip/32/512781_2.png) [@zogstrip](https://meta.discourse.org/u/zogstrip)
#### Post date: [February 9, 2026, 1:30pm UTC](https://meta.discourse.org/t/allow-mark-as-solution-in-group-messages/370496/29 "2026-02-09T13:30:59Z")

</div>

Good news @here, it’s coming back 😅

> <https://github.com/discourse/discourse/pull/37635>
>
> PM support for the solved plugin was intentionally removed in https://github.com…/discourse/discourse-solved/pull/334, but multiple communities rely on solved in group messages for private support workflows (e.g. using Discourse as an internal ticket system).
> 
> Add a new \`allow\_solved\_in\_groups\` site setting (group list, default empty) that enables the solved UI for group messages belonging to the configured groups. Regular 1-on-1 PMs remain excluded.
> 
> The implementation adds an early return in \`allow\_accepted\_answers?\` for private messages that checks whether the topic's allowed groups intersect with the configured setting. The category/tag logic is extracted into \`solved\_enabled\_for\_category?\` so callers without a topic object (e.g. the category-change diff in plugin.rb) still work. All existing PM exclusions (reports, badges, filters, directory columns) are intentionally left unchanged.
> 
> https://meta.discourse.org/t/370496

---

_[View the full topic](https://meta.discourse.org/t/allow-mark-as-solution-in-group-messages/370496)._
