# Managing product announcements with multiple versions

**URL:** https://meta.discourse.org/t/managing-product-announcements-with-multiple-versions/404039
**Category:** Community Building
**Tags:** notifications
**Created:** [May 28, 2026, 8:45pm UTC](https://meta.discourse.org/t/managing-product-announcements-with-multiple-versions/404039 "2026-05-28T20:45:58Z")
**Posts on this page:** 1
**Showing post:** 3

<div class="post-metadata">

### Author: ![putty](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/putty/32/370902_2.png) [@putty](https://meta.discourse.org/u/putty)
#### Post date: [June 4, 2026, 9:02pm UTC](https://meta.discourse.org/t/managing-product-announcements-with-multiple-versions/404039/3 "2026-06-04T21:02:02Z")

</div>

Thanks, Hawk, this helps a lot.

> [@HAWK](#):
>
> Discourse supports fairly structured tagging with tag groups, parent-child tag relationships, limiting one tag from a group, and category tag restrictions, so you can keep this from turning chaotic.

I think establishing tag groups and mandating/restricting their use will help a lot. That level of control slipped my mind.

> [@HAWK](#):
>
> If you have one release topic tagged with both product and new version
> 
> - category: `Release Notes`
> - tags: `1secure`, `v10.8`

My reluctance to separate the product from the version is that they’ll be notified whenever someone uses the 1secure tag, even in a support-style topic. Still holding out hope for subscribing to tags per category 🤞 😬

Though I guess the potential answer there is to restrict 1secure from being used in those support categories, since it’s already denoted as 1secure support.

---

_[View the full topic](https://meta.discourse.org/t/managing-product-announcements-with-multiple-versions/404039)._