# Automatically Mute Categories When a User Leaves a Group

**URL:** https://meta.discourse.org/t/automatically-mute-categories-when-a-user-leaves-a-group/357040
**Category:** Feature
**Created:** [March 12, 2025, 10:14pm UTC](https://meta.discourse.org/t/automatically-mute-categories-when-a-user-leaves-a-group/357040 "2025-03-12T22:14:51Z")
**Posts on this page:** 1
**Page:** 1

<div class="post-metadata">

### Author: ![emonunix](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/emonunix/32/485652_2.png) [@emonunix](https://meta.discourse.org/u/emonunix)
#### Post date: [March 12, 2025, 10:14pm UTC](https://meta.discourse.org/t/automatically-mute-categories-when-a-user-leaves-a-group/357040/1 "2025-03-12T22:14:51Z")

</div>

Hello Discourse Team & Community,

I’d like to propose a **new feature** that would allow categories to be **automatically muted when a user leaves a group**.

### **The Problem**

- When a user **joins a group** , they can be set to automatically track its related categories using **Group Category Notification Defaults**.
- However, when a user **leaves the group** , they continue seeing those categories in **Latest** , and their notification settings are not reverted.
- Manually muting the category for each user after leaving a group is not practical, especially for large forums.

### **Proposed Solution**

- Introduce an option in **Group Settings** to **automatically mute or reset category notifications** when a user **leaves a group**.
- Alternatively, extend the **Discourse Automations Plugin** to include a **“User Leaves Group” trigger** that allows muting related categories.

### **Why This Matters**

- Keeps the **user experience clean** , ensuring users only see content **relevant to their selected groups**.
- Reduces clutter in **Latest** for users who no longer belong to a group.
- Helps maintain **better organization** in large forums with **public groups and open categories**.

### **Potential Workarounds**

- **Custom Wizard Plugin** : Could be an option, but currently requires user interaction to trigger changes.
- **Custom Automation** : Would need development, but no built-in solution exists today.

I’d love to hear thoughts from the community and Discourse team! Would this be possible to implement in core, or would it be better suited as a plugin update?

Thanks in advance!