Group-Level VIEW ONLY Permissions
While I'd like to see some more granular permissions in general, I would like to see at a minimum a VIEW ONLY option assigned to users in a Group / Plan.
Right now everyone is a contributor and everyone can do everything, but there are lots of situations where we want to give situational awareness to certain users, but not let them edit group documents, or potentially delete things (not out of malice, but just unawareness).
You already get at least the basic Viewer/Contributor model on most other services, like SharePoint team sites, Yammer groups, almost all of the project management tools, etc.
you can do this in SharePoint today (i.e. put all members into Read Only permission bucket)
We really need to be able to prevent folks from updating the group calendar - only 2 people need write access, and everyone else should have read only. Why would I shift to Sharpoint for this? We should be heading towards using NEW technology and not old.
Any status update on this?
I'd like guests to be able to receive emails sent to the group, but not be able to reply. This would allow a basic mailing list (e.g. Mailman) replacement. DGs are not good for allowing people to unsubscribe themselves, which is an important consideration these days. O365 groups do allow people to unsubscribe, but in the meantime it doesn't mean they should be able to email everyone else in the list.
Jeremy Miller commented
Agree with others here. Simply changing permissions in SharePoint does not fulfill the original ask. In the SharePoint only scenario suggested, how does this affect the Exchange pieces of Groups? Seems the "read only" user would still be able to make edits to the conversations, calendars, etc.
Philip Worrell commented
I think you will find this item is about group specifically. Scenario where you have a private group, you have your owners and members, but you may want to give group access to other to see your information in conversations, planner, sharepoint etc, but not have them directly contribute.
It goes against general collaboration in some ways as why be able to only read something and not be able to respond, but I can see situations where this would be required. Where people need read access but should not be able to modify a conversation or, plan or file.
Ron van de Ven commented
I would like to see a wider implementation of what is already available in sharepoint across all services that draw on an office group. Meaning Planner, Teams & Outlook as well instead of only sharepoint. We can hardly work with public groups, but for each group there can be several stakeholders that we like to be informed but not mess things up sort of speak.
It would be really helpful to have the following user permission options:
1) Files area is read-only (user cannot upload or change documents) and user can download documents stored in the group.
2) Files area is read-only (user cannot upload or change documents) and user cannot download documents stored in the group.
Marlo Bell commented
Another side effect of this is that documents aren't searchable to the general population. There is a situation where users aren't deeply involved in a group, but the information is still beneficial. Our company has tried to adopted a Knowledge Management mantra of "no harm in knowing", in that documents should only be locked down when they NEED to be locked down.
Ditto on permissions within group file/document libraries
I want this too
Amber Imes commented
Having the ability to grant basic read/write and read only privileges would be hugely helpful in Groups. I hope Microsoft adds this feature soon!
Thomas Dreisig commented
It is really a good idea to work with permissions. In schools teachers need to setup folders with different permissions.
Merritte DeBuhr commented
I agree with all the comments about the need for more control over permissions. We really need a way to prevent members from modifying the site pages and adding applications. This seem to be a major oversight.
Is there a timeframe for this update? It's really needed for our organisation!
Christopher Woodward commented
This is so important. I can't modify the Group Member to Read anymore. I was able to. At least you can modify EDIT to essentially be Read Only which is my temporary workaround for my Power BI Reporting Groups. I can't have my reports modified by anyone other than the Group Owners.
Dave Barnett commented
IF you do View only please allow them to download or save a copy of the document.
Marek Staniewski commented
The groups have 3 type of users. Owners, members and quests.
I can imagine, that MS is going to use this 3 subgroup do make different permission.
I would them suggest that as guest it is possible to add also standard users (not only a person outside organization). In this case there would be more flexibility in designing different permissions without reconstructing current group structure.
For example Owners could edit site, members edit libraries and guest only read libraries.
By the way:
Would it be possible to make the permission only to see the lists but without reading content of elements?
Marek Staniewski commented
Would be good if there is a possibility to make more than read only permission. What problem would be to add different premissions to members?
In case the new member will be added he may initailly get lower permission, which is acttually in group.
I believe it is possible to have both: fixed permission as it is now and still to have chance to make them different.
Wher the group is established then all could be as it is now. This mean that all members have the same rights. But group owner should be abble to set differentiate permissions and from this moment every new member should get the lower permission the group posses.
I believe that fact that permissions cannot be changed is actually a biggest problem to use new groups in SharePoint.
What's the status on this? Really need view only permissions
I know this has been pitched before, but adding subgroups would also be helpful I believe. While having different file permissions for each user would be great, in my case, I would prefer to give a subgroup the ability to only view & edit certain Group files. Then, once the subgroups are setup and the file access for each established, I can assign users to a subgroup which would then have the permissions and file access already established. This would minimize the chance of forgetting to provide the correct access to a specific Group file(s).
What's the status on this? Really need view only permissions for Group Calendar.