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)
Khai Do commented
Do we have an update on this topic? this is a much needed feature for our organization. I've been looking forward to see this implement!
Adam Duggan commented
Agreed! One way we'd like to use Groups is as a shared knowledge base. Users are comfortable with using an email distribution list to discuss topics and ask/answer questions, and this is a great way to archive that content in an accessible and searchable fashion. However, to open this to a broader audience requires the ability to restrict deletion of the messages (or at least restrict deletion to only messages that user created).
Brett Hinton commented
One idea that this would help with is if some members of the group could add group calendar events (but not everyone).
ACS Sys commented
I agree, sharing files without some control over how things are shared makes little sense in a group environment with multiple types of members.
Don Loughran commented
Agreed. A group creator might want to mark documents "view-only" for many reasons, none of which warrant abandoning groups for a team site or alternate storage location. In general, I think that any document storage should have the ability to restrict editing as a basic capability.
Craig Brown commented
This is a much requested feature in my org as well. We used to use Lotus Notes Team Rooms, which had more granular permissions. We like the use of groups for simplicity, however the users want more control over the data as not everything should be editable.