That’s the change I thought we were going to make. The way it is now is wildly inconsistent in muted topics vs muted categories.
I made that copy update, but we really need to confirm that muting a topic will hide it from latest as well.
I created a new category called ‘Canned Responses’ that has about 20 topics in it. We use this category for our ‘Discourse Templates’ so I don’t want them showing up in my Latest feed.
I went and added the category to the ‘default muted’ list and it asked if I should update for existing topics and I said yes.
They still showed up in my latest list. My best guess is that because I’m the author of all those topics that it excluded me from the muting, but I don’t want to see them as they’re just templates.
I used bulk update to mute them all but now they’re missing from both latest AND the category list.
It appears to only be an issue for me. I logged in as another user that has permissions to see the Canned Responses category and they are able to see them in the category but don’t see them under latest.
Is there a setting that will hide them from latest, but not hide them in the category for author? As other users start adding topics to the category I’m guessing they will show up in their latest feed too.
And finally, it appears that the text is inconsistent with what happens.
It says it will be hidden in latest, but does not say it will be hidden in the category as well.
There are some peculiarities between topic level notifications and category level notifications. The first one is as you’ve found out, the topic level notifications take precedence. So if you have a topic set to Watching and mute the category then that Watched topic will still stay as Watched (and act as such). And you’re right, any topic you create is automatically set as Watching, so muting a category won’t clear your own topics away from Latest unless you manually change the topic level notification.
The second is the difference between a mute at the topic level and a mute at the category level. The topic level one is slightly more aggressive.
I think what you want to do for your template category topics is to go to your canned-responses category and look at all of your muted topics (by adding ?state=muted to the category url eg. https://meta.discourse.org/c/feature/2?state=muted) and then use the bulk actions again to select all the muted template topics and set them to ‘normal’. And if you still have your canned-responses category set to muted at the category level they should now be absent from /latest but still show in the canned-responses category.
You can see an example of it here in Site feedback > Forum summaries, where the category is default muted to hide the topics from /latest, but they’re still findable in the category itself.
Does that make sense?
כן, החלפתם בחזרה למצב רגיל נראית כפתרון.
האם יש דרך לגרום לנושאים שאתה יוצר בקטגוריה מושתקת להיות מוגדרים כרגיל במקום במעקב כברירת מחדל?
אם לא, אני פשוט אכתוב תיעוד פנימי כדי שאף אחד אחר לא יתאכזב.
No, I don’t think there is anything that can do that currently. Though having the template topics show up as normal is no bad thing. I’ve found it useful to see when anyone posts to them with suggestions for changes, for instance. Or being able to see when someone creates a new one. If no one posts then they’ll drift down the stack of /latest as normal and are generally no bother.
אני מסכים. רגיל זה מה שאנחנו רוצים.
אם הקטגוריה מוגדרת להשתקה, אבל אתה מגדיר את הנושא שלך כרגיל לאחר יצירתו, אז אתה מקבל הודעה אם עונים לך או מזכירים אותך (@mentioned), אבל זה גם לא מופיע ב-/latest.
אה, אני חושב שהייתה כאן אי-הבנה. לגבי רמת ההתראות ‘רגיל’, התכוונתי לכך שזה לא דבר רע שנושאי התבנית מופיעים ברשימות הנושאים של /latest (et al).
אה, ובכן, אני בחוסר הסכמה מכבד. כשאני צריך להיכנס ולכתוב 20 או יותר בבת אחת הם מכבידים על ה-/latest שלי, והם זמינים רק לצוות התמיכה כך שאף אחד אחר לעולם לא צריך לראות אותם גם ב-/latest.
הרגע כתבתי מסמך צוות שמציין שכאשר יוצרים תגובה מוכנה חדשה, השלב הסופי הוא להגדיר את רמת ההתראה ל’רגיל’.
No worries.
The option is there to hide them, and you can always flick the category back to ‘normal’ if you ever change your mind, so it’s very much a player’s choice scenario. ![]()

