Mike Khirallah

Hi Kasper,

Thank you for your response and your example use-case that counters my use-case. The reason I used the word concerned was specifically because I could not tell if this was the intended behavior, and since Zendesk User Segments are the only means of configuring authorization for end users, it was wrongly assumed that those segments would encompass both Gather topics and @mentions to users who have access to specific topics.

Based on your response, it was clearly intended behavior to be able to mention other users across topics and therefore, user segments. Just to provide more context as to why it is a PII issue for my use-case, people in different user segments should not know that other people (or other topics for that matter) even exist - each topic is designated to a single set of users. So when I was testing the new @mentions feature after turning on the profiles feature, I did not expect to be able to see users that were not in the given User Segment to show up.

Thank you again for your confirmation that this is intended behavior and the simple solution for our team is to keep the profiles feature disabled in order to prevent cross-topic mentions.

 

 

When utilizing the User Segment's feature to allow only certain users access to certain topics, I expect that the mentions feature to also apply filtering on the Zendesk Backend so that only individuals who would be able to access the given forum via user segment would be able to only mention people that the resulting authorization would allow based on:

1. user segment
2. admin role

The screenshot below does not provide an extensive amount of context due to privacy, but this is demonstrating that everyone in our entire community (anyone who has access to any topic) can mention anyone else, which is concerning and has prevented me from turning on profiles (for reference, I've selected private profiles and it makes no difference).

 

Is this expected behavior?