I would like to create a read-only team
I would like to create a team that is for everyone in the organization. I can do this already with dynamic membership. The purpose would be to provide access to team members to see documentation such as employee manuals, corporate policies, and other read-only content. Admins can add/delete material while everyone else has read-only access.
Erik Pauwels commented
Mainly for Files. It was strange to discover that Guest was not the read only member group in Teams. It usually is. Now we are forced to make permission changes in SharePoint.
Teams so GREAT but this is stopping us from moving to it 100%
Would be very good for advisory channels where other users shouldnt post anything
Would be Perfect for advisory channels like IT-Operations issues--
Our organisation needs public teamsites where only a set number of owners have rights to edit content.
Ben Leach commented
I agree with this request...there have already been "Org-wide Teams" that have been rolled out, auto-enrolling everyone into the Team, but having an Org Wide Team that is read-only for majority of users could almost become like an Intranet style Team Hub for core documents and knowledge that people need to have access to...without having to take them away from the Teams interface to look at a comms site.
The other reason for this is that you could create Teams that behaved as Templates for others to use, with the right configuration of channels and Tabs, say for a new project. People can be a member of that Team so that they can see it and Clone it, but without being able to modify the template itself
Brian Riesen commented
Not everyone with access to information should be able to edit that information. Having a "Visitors" group level, in addition to Owners & Members, like traditional SharePoint sites do, would be a welcome addition.
I agree. We need to be able to lock down Wiki and Files with read-only. Currently I can't make various teams available to the wider company because of not being able to restrict access. For now we have to stick with Confluence.
I agree. We have "Team Leaders" who would like to post a document or spreadsheet in a read-only fashion in the obscure location called "Files". Without the proper permission settings, we have had "Members" edit the files as well as delete said files "by accident". This one issue is causing our entire organization from embracing Teams.
We can lock down the "Conversations" tab but not the "Files" or "Wiki".
Similar to this, our team doesn't want to expose our entire Team as readonly, however we have a subset of channels that we would like to make readonly across the company, so that customers can track threads related to certain features