Overview
Release 2026.006 includes customer-facing improvements focused on filtering clarity, scoped tagging compatibility, and API flexibility.
Schedule
- Staging: (Tentatively Week of April 20th) but delayed to April 27th
- Production: Week of April 27
- Enterprise: Week of May 4
Tag Following
Users can now follow tags to stay updated on the topics that matter most to them across the community. When new posts are published with a followed tag, users can receive notifications based on their preferences, creating a lighter-weight way to support discovery and ongoing engagement.
This includes a new ability to set an optional description for tags as well:
You can also review your followed tags and decide if you want to get pop up or email notifications by default and by tag (similar to how our category following works today)
You can set the default preference for the above in User Preferences to decide how noisy you want this to be by default.
Tags added to Followed Content:
Read more in the docs:
https://success.vanillaforums.com/kb/articles/1889-tag-following
Tag Cloud widget now supports more filtering and sorting options
The Tag Cloud widget now includes new configuration options that give admins more control over which tags are shown and how they are organized. Admins can filter the widget by category or subcommunity, including contextual options on supported page types, and can sort tags alphabetically, by usage, or by date created.
This update also improves compatibility with scoped tagging behavior. When filtering by category or subcommunity, the widget is designed to include both global tags and tags relevant to the selected area, helping surface the most useful tags without hiding global ones unnecessarily.
This is especially useful for landing pages, subcommunities, and other complex community setups that want to create more curated or segmented experiences. It is particularly valuable for communities with multiple products or more advanced content structures, where admins want to clearly show which tags are relevant within a given area of the community.
Note that to use these filters, Scoped Tagging must be enabled.
Discussion lists now show active filters more clearly
Discussion list headers now make the current filter state easier to understand without needing to reopen the filter dialog. Applied filters are surfaced more clearly in the page header, helping people quickly see how the list is currently narrowed.
This is especially helpful when linking people to a specific filtered view, including tag-filtered views, so they can immediately understand that they are looking at a curated subset of discussions rather than the full list.
This update also includes an updated clear pattern and pagination-related UI adjustments to better support filtered browsing.
User API now supports expand=isSsoUser
The users API now supports expand=isSsoUser, making it easier to tell whether a user account is connected through SSO or created directly in the community.
This gives developers and technical admins a simpler way to tailor integrations or downstream experiences based on account type. It is also helpful for communities that want to better understand their user population and analyze where end users are coming from.