Forum Discussion
MicrosoftUPDATE: Create Office 365 Groups with team sites from SharePoint home moving beyond First Release
What impact does setting the Group Members to Read on the sharepoint site have on Group Files, Notebook, etc (like from the Groups UI, and Groups mobile app?)
I assume any of the Group workloads that technically live in SharePoint would just become read-only?
Also, is there the possibility to do any kind of different permission levels for standard Group roles
- Like make Group Members Contributors instead of Editors
- Make Group Owners Editors, not Full Control
- etc?
MicrosoftBTW, there is a way to achieve the shift of members to 'Contribute' from 'Edit'.
1) Create a new SP group, e.g. "Foo group Contributors" and assign it 'Contribute' permission level
2) Grant permission to this new SP group
3) Add the 'Foo group' member claim to this SP group
4) Delete the 'Foo group' member claim from the 'Foo members' SP group
Net effect is to give contribute permissions to group members, however the simple UX will only show the 3 default SP groups. Per my previous post, we're looking at adding a contribute bucket in the panel to simplify.
- Hi Tejas,
I'm trying to do step 4 in your post but not having much success in deleting the 'Foo' group from the 'Foo Members' SP group. In 'Site Settings - People and Groups - Foo Members' UI, the 'Foo' group can't be selected like any other group member as the checkbox is grayed out. I've also tried creating a new 'TestGroup' and adding 'Foo' as member with the same issue - checkbox grayed out preventing member from being deleted. From the Sharepoint mgmt shell I've tried the following command:
Remove-SPOUser -LoginName foo@company.com -Site https://<orgid>.sharepoi
nt.com/sites/<foo> -Group "TestGroup"
For LoginName, I've also tried the Foo group GUID given by:
Get-SPOUser -Site https://<orgid>.sharepoint.com/sites/<foo>
They both return the error "Remove-SPOUser : The user does not exist or is not unique."
Could you please point me in the right direction to delete the group from group membership?- Tejas Mehta
Hi Proliance - there is a pending fix to the problem you're seeing where the remove action is greyed out for the member claim. Until that fix shows up in your environment, there is a workaround. From the modern permission panel, simply move the group members from Edit to Read. Then, make sure that the member claim is added to the new SP group you created with the 'Contribute' permissions.
Net effect will be what you desire. You will see members have 'read' permissions in the modern panel, but under the covers they actually have 'Contribute' from the addition to the new SP group.
- Thanks for the info Tejas. The one tenant we manage has yet to receive the modern permission panel update as they're on Standard Release. I do see the panel in our own First Release tenant environment though and it's great - really appreciate these recent updates!
We'll wait on the rollout of the updates. Thanks again!
- The bucket for Contribute will be great! My recommendation would actually be to make Contribute be the default. I think you'd find a lot of support for that in this community (both the bucket and the default)
- +1 for Brent's suggestion to make Contribute the default!!!
- +1 to Brent's suggestion: make Contribute the default bucket
- Also :) +1 to Brent's suggestion: make Contribute the default bucket
