Haworth is requesting the ability to restrict tag visibility.
Problem Statement
The legal team requires a method to organize and label sensitive content with a dedicated tagging structure. This structure must be private and accessible only to members of the legal team. Currently, all tags are public and visible to every user in the instance, which can lead to:
-Confusion for other users: Tags with no associated content for other teams clutter the user interface and create ambiguity about their purpose and relevance.
-Difficulty in managing private content: There is no efficient way for the legal team to create and maintain a clean, hierarchical tagging system for their restricted documents without exposing it to the entire organization.
Proposed Enhancement
A feature that allows for the creation of restricted tagging hierarchies, possibly by collection. This would enable specific groups or teams (e.g., the legal team) to create and manage their own private sets of tags.
Key features of this enhancement would include:
-Group-Specific Tag Visibility: Only members of a designated group would be able to see and use the restricted tags.
-Clean Tagging Trees: The ability to build and maintain a clear, hierarchical tagging structure without it being visible or usable by other users.
This enhancement would greatly improve the team's ability to organize sensitive information securely and efficiently, while also providing a cleaner and more intuitive experience for all other users.
