Pain point: Currently, I am getting the complete list of invited readers who can access our Knowledge Base. On the invited list, there are a few readers who are our employees, and the rest are our customers. Both have created reader accounts using the email invitation. With the current data structure, understanding the usage patterns of "External" invited readers (who are the customers) in mixed projects is challenging.

Request: As a KB administrator, I propose a solution to segregate the reader types. This request proposes the development of user-tagging functionality within the Knowledge Base (KB) management system. This feature could allow administrators to assign tags for each user, such as "Internal" and "External," while creating the user accounts. This data (tags) can be displayed against each user as a column within the Analytics > All Readers table. So that administrators can easily filter the data as required.

Benefits:

* Enhanced User Segmentation - Understand how external readers (customers) interact with your KB compared to internal users.

* Streamlined Data Filtering - Effortlessly isolate data specific to external readers for targeted analysis.

* Improved Reporting - Generate comprehensive reports that differentiate user behavior based on internal/external tags.