1 person found this helpful
Hey Bryce Williams -- we have an internal and external environment so I'll give you my perspective on the Share button for both use cases:
- Internal: we decided to leave it on because a lot of people have liked using the feature. We don't spend a lot of time with e-discovery so it's not a huge deal. To be honest, I much prefer @mentioning people in either the body of the content or the comments section. This achieves the same notification goal and also makes it visible to others
- External: we disabled this feature because we cannot see the replies to shares AND the share button creates a PDF version if it is shared externally. Our security team felt like it was a little too risky to allow content to leave the community that easily
Hi Jeffrey (Jeffrey Murnan),
Regarding part of your second bullet:
External: we disabled this feature because we cannot see the replies to shares
Why can't you? Shares show up in my inbox. Maybe your admin has this disabled? (I mean before they disabled shares altogether)
It's kind of weird, but you (or at least we) have a record of replies to shares, but there is no record created when you share something with someone. I would like to be able to see what all I've shared with someone in case I want to follow up with them.
Hi Grant Whitacre -- what I meant by that is:
When people share something, others can reply to that "Share" and that content is not easily visible to community admins.
Since I wrote my reply, we have actually had a change of heart and plan to enable Sharing within the next week. We decided it was worth it and decided to use a few Phrase Substitutions to clean up the wording so users clearly knew not to share outside the community.