MicrosoftWhat happens if you post a news story from a team site to an Engage community channel where members of the Engage community channel are NOT members (or visitors) of the team site. Will they see the post but not be able to click into the SharePoint site news post or just not see the news post at all?
How does this function handle different permission scenarios?
Microsoftgreat question, yes, they will be able to see the SP News post. They can click into the site to see it on SP or simply continue seeing on Engage, both will work.
The Engage community users who are not members of the site will NOT get access to other content on the site. They will ONLY be able to see that cross-posted SP News post as it was shared to them (Engage community).
ReetikChandra Mmmm - so another Microsoft oversharing mechanism that breaks inheritance on the pages and you end up with a site that no one knows who has access to what - sounds familiar. The entire sharing solution that Microsoft keep enabling is absolutely horrible for governance (something Microsoft has forgotten about a long time ago). Sounds like we need to do some further testing on this feature. As someone else mentioned, will there be a way to disable this in our tenant, or enable only for certain users or sites - PLEASE?
Microsoftgrant_jenkins, Thanks for raising this. To clarify my earlier reply, cross-posting lets the chosen Engage audience see the news post without giving them access to other content on the SharePoint site. This follows the existing ability for an author to share their news post beyond the site’s audience.
We remind authors to review the Engage audience before posting, and site owners can also set a recommended community for their site’s news.
There isn’t currently a tenant-level opt-out or a way to restrict the feature to selected users or sites. I understand why that control matters to your organization, and I’ll share your feedback with the team.
