Skip to main content

Guru content owners are adjusting to the new announcements (formerly Knowledge Alerts) and coming up with some great questions and ideas on them.

One of our authors mentioned that all recipients can see who else on their team has read the announcements - this may work for some teams but I’d love the ability to turn off this feature. It opens the door to users “checking up” on their coworkers when the read vs unread info is most useful to the sender of the announcement. 

Hi @Anna Stout - I feel similar and had a concern with a post in the Product Feedback under the initial announcement. It was not explicitly announced that all “View Only” recipients could see the details (not just percentage) and/or export the details as well so I was not sure if this was intended to work as designed.

I also had a read only user say they clicked the actionable “Export Data” Button that was presented to them and did not receive the detail in their email, even after checking spam.   Was this your experience also for view only team members? 

 


We didn’t have any read-only users look at exporting the data, but we did have one confirm she could see each individual user’s read/unread status of the announcement. I spoke with someone from Support and they confirmed that is how the announcements are designed to work. 

My big concern is the ability for recipients to drill down to the user specific level of this data. In and of itself, it’s not bad, but I could see it leading to undesirable situations. Example: In a performance coaching conversation, the user being coached may use this data to call out other employees’ habits and performances to justify their own. 

I guess because my company considers use of Guru as part of our performance evaluations, user activity feels like sensitive data that should only be exposed to management and the user in question. 


Thank you for sharing this feedback @Anna Stout and @Linda Moore! Yes making read stats visible to everyone is working as intended. Teams often collaborate around announcements, so it helps to not have to ask senders to copy and share the stats as an additional step. Hearing about your particular situation and context is really helpful - I can see how the added transparency adds complexity in that case. Appreciate you sharing that!

I can’t promise that we’ll change the UX, but we will definitely consider your input here for future iterations. We will also keep an eye out to see if this is a common situation. Leaving this thread open so that others can upvote and chime in.

Thanks again!