Restrict Users from "Share in community" but still permit viewing the community
P
Phil Ellis
I've seen a few instances of internal information being accidentally shared in the Community and often from MSPs themselves. Agents and Workflows that reveal sensitive information that were clearly not intended to be shared publicly, as they have since been removed. In order to prevent such incidents, I would like a setting or role adjustment for MSP Users to prevent them from having "Share in community" permission. I see we can disable community entirely, but for adoption/onboarding having ideas from the community is so very beneficial, at the same time during adoption/onboarding, people are the least informed about the platform and may not understand that "Share in community" is essentially public.
J
Josh Campbell
Agreed, this would be a valuable addition. The ability to restrict "Share in community" while still allowing viewing covers the immediate risk of accidental disclosure, but it would also be worth extending that control further.
Specifically, if admins could configure whether users can view the community at all, it would be useful to pair that with an option to limit what community content is visible, Hatz Official or All. That way, during onboarding especially, users are only exposed to vetted information rather than the full unmoderated community feed. It keeps the value of community learning intact without the risk of newer users acting on unverified or premature content.