01-04-2017 02:12 PM
01-04-2017 02:12 PM
In a SharePoint site attached to a Team, Team Owners group gets Full Controll permissions level, and Team Members group gets Edit by defaul (can be changed to either Full Controll or Read). Then there is Read permissions level that is not assosiated with any Team groups.
Will the Teams app have an option to add users as Visitors (in addition to Owners and Members) in the future?
01-05-2017 06:02 AM
Yes, that can be achieved by opening the site, going to Advanced sharing settings, opening New Team Visitors SharePoint group, and finally adding people to it. Setting up a shortcut on the home page of the site would ease the burden for users, but they would still have to remember to go to two different places to manage the same set of permissions levels.
I find Team's approach to managing permissions very intuitive and convenient, but think that it's incomplete without Visitors (Read) component.
01-05-2017 03:19 PM
I've been thinking about this also, and I can't think of any good use cases for 'Read' level permissions in a chat room. Isn't that just watching a text version of a video or Skype Meeting Broadcast at that point? Aren't chat rooms meant to be collaborative?
01-06-2017 11:10 AM
I agree. There is probably no practical use for Read-only permissions in conversations. My primary concern is with content stored in a linked site.
In the first screenshot (Site permissions), in my original post, there is an option to change permissions level of Members group to either Full Control or Read. After switching from Edit to Read, members of the group can still participate in conversations and navigate file directories, but loose ability to upload/delete content.
That's precisely how I would like Visitors group to behave. Allow unrestricted participation in conversations and provide view/download access to content.
04-13-2018 07:59 AM
We have a specific ask to allow a generic account (shared device) access to monitor a Teams channel so it can be displayed on a large monitor in the NOC. We don't want to give the generic account a license or potentially allow that Username to post content without accountability. Read only on the team would be perfect.
09-17-2018 11:54 AM
yes- that's it- we don't use Yammer her- failed adoption in the past makes it a non-starter. so looking for a work around...
09-04-2019 02:20 PM
Did this ever go anywhere? I have exactly the same use case. I don't want employees to be able to delete content (it's for DR/BC Team) but I do wan them to be able to read all of the content and add their thoughts to the chats etc. @Alexandre Ivanov