Jan 09 2020
01:06 AM
- last edited on
Feb 06 2023
04:06 AM
by
TechCommunityAP
Jan 09 2020
01:06 AM
- last edited on
Feb 06 2023
04:06 AM
by
TechCommunityAP
I had an Office365 consultant here and he told me that if I put visitors in a SharePoint Teamsite that is connected to an O365 group, this is a bad practice.
He explained, that an O365 group (team, calendar etc.) does not have visitors and we should avoid doing so.
However, many people here want to give some other people reading permission.
Often people that are no direct collaborators should at least view some documents.
The consultant told me, that putting people in the Visitors group is not straightforward and not recommended by Microsoft.
The alternative should be using a communication site and publish the read-content there.
But my users struggle a lot with this, because they do not understand the purpose to copy files to a communication site. (Not to mention that they are of cause not able to create a flow to do this)
For me as an admin it also seems pretty complicated to publish things to a flow, when live could be so easy, just adding people to the visitors group.
How do you handle this?
I thought a short time about sharing a link, but for many files this also is not practiacable...
Jan 09 2020 01:47 AM
Jan 09 2020 02:09 AM
@adam deltinger Okay, thats good to notice. But then its hard to me to get the concrete sense of communication sites. We have very often Teams that work together and they want to publish only some or all content as read to other people.
What about the argument of our consultants that a Team site is about collaboration, not publishing?
Jan 09 2020 02:32 AM
SolutionJan 09 2020 02:35 AM
@adam deltinger And on the communication site I just put a hyperlink, referencing the public team. Did I get you right?
Good to know btw. that communication sites are more for site pages and not for files.
Jan 09 2020 02:54 AM
Jan 09 2020 02:56 AM
@adam deltinger okay, got you! Thanks.
Jan 09 2020 02:32 AM
Solution