Feature Request

Problem Statement: The KB documents a hard 1,000-tag cap but no in-product mechanism (comparable to the AI writing agent's 80%/90%/100% usage notification emails) for warning administrators as they approach the tag limit. Without this, customers may not discover the limit until they are blocked from creating a new tag. Suggested Enhancement: Add usage threshold notifications for the tag library (e.g., at 80%, 90%, 100% of the 1,000-tag limit), mirroring the existing notification pattern already used for AI writing agent credits. Customer Benefit: Gives administrators advance notice to clean up or consolidate tags before hitting a hard block, reducing workflow disruption. Priority: Medium — this is a genuine gap since the KB confirms no such notification exists for tags, and a directly comparable pattern already exists elsewhere in the product for a similar type of limit.

Currently, tags are displayed based on creation order instead of alphabetical order in both the article settings tag selection dropdown and Manage tags section. The customer would like tags to be sorted alphabetically to improve usability, especially for new users and larger teams managing a high number of tags. This enhancement would make it easier for users to quickly identify and select the required tags without manually searching through randomly ordered entries.

The customer frequently uses the term OMS+ in their articles, and Eddy rightly recommends it as a tag. However, the system currently doesn’t allow them to add tags containing special characters like +, which creates a blocker for their workflow.

we need to group the tags belonging to a group of devices or one of our services so that while tagging the article you need to tag the group so that the individual tags will be added to the article. If one new devic is added to this group, only the tag has to be added and all documents will also be shown if you search for this new device..

Provide a UI to allow for multiple articles to have the tags edited.

When an article in reader group B is linked from an article in reader group A and the source article has a tags A and B; When I click a B tag I should see the article that is in group B, but I don't. Can you make that happen?

We are currently using multiple project versions to stage our Documentation - a Beta Version to allow SMEs and Technical Writers to develop the actual documentation and a Live version that is available to clients and employees. Due to this as well as the organizational structure of the KB, we want to utilize the tag management functionality to help us group articles in the event that we have to update several documents pertaining to one system quickly. However, there is currently no way to filter the articles within the tag management system either by searching a specific project version (search the printer tag under only the live version - no beta version results) or by grouping multiple tags (i.e. all documents that contain the tag live AND the tag printers). Either of these options would be immensely helpful.

We are planning to use the tags to be able to search and manage all articles related to certain systems or departments. However, we would like to be able to set permissions for who is able to create and/or use tags to ensure that we don't have to constantly clean up the tags (duplicate tags, misspellings, etc.).