Recommended way to change the Modern Team site's Member group permsion level from Edit to Contribute

Steel Contributor

I have created a new Modern Team site and i got 3 security groups created for us, as follow:-

 

editmemebrs.png

 

but the problem i am facing is that the "Site Member" will have Edit permission, while i want them to have "Contribute". and modifying this from the UI will not be possible, as the "Edit User Permission" will be disabled. now i read many links about this problem, and seems we can modify the Edit permission level using power shell, but lot of folks mentioned that this is not recommended.. today i came across this link which is written by an MVP from Microsoft https://www.dontpapanic.com/blog/?p=526 and the author mentioned that we can overcome this problem by adding a new security group inside sharepoint and grant it Contribute permission. so my question is if this option is considered a valid approach to solve editing the permission level for members?

 

second question. now i had an idea, is that instead of creating new security group or run power shell script, can we go to the "Edit" permission level, and grant it permissions similar to the ones inside Contribute permission level? so in this case "Edit" permission level will be "Contribute".. so is this a valid appraoch ?

 

editpermison.png

5 Replies
What I would do here is what we have done always with SharePoint in regards of permissions: just create your custom SharePoint Groups with a specific permission and add your users / security groups there (ideally this). I don't recommed you to try to modifiy default security configuration created when the site is created

@Juan Carlos González Martín wrote:
What I would do here is what we have done always with SharePoint in regards of permissions: just create your custom SharePoint Groups with a specific permission and add your users / security groups there (ideally this). I don't recommed you to try to modifiy default security configuration created when the site is created

@Juan Carlos González Martín   thanks for the reply. so in a way or another to follow the approach mentioned in this link https://www.dontpapanic.com/blog/?p=526 ?? is this correct?

 

second point. now if i create a new sharepoint security group and i grant it a contribute permission (while i leave the built-in "Site Members" which have Edit permission level empty), then i will loose the benefits of having a real SP modern team site? is this correct? i mean sharepoint modern team sites, assume that the built-in "Site Members" contain users, so they can use the shared calendar,shared mailbox, planner ,etc.. but having users added to the sharepoint modern team site using a sharepoint group (rather than relying on the office 365 the built-in "Site Members" ) will minimize the benefits of having Office 365 modern team site. is my point valid? and maybe it will be better to have a communication site instead of having SP modern team site in this case?

@john john Hi. Did you get anywhere with this. I have the same issue. My client has a Teams site which is shared with external guests. We need all the team members to have the 'restricted view' permission level.

I can create another SP group with the 'restricted view' permission level and reroute the O365 group to it. But then if a Team member adds a guest in the Teams front end, the guest will go into the team members permissions group and get edit permissions. My clients want to add users themselves, which seems to me to make sense. 

Alternatively I can change the default team members permission level from 'edit' to 'restricted view' in site permissions. Then if a member grants access to another they will get the correct permissions. But should I? It seems to be working but I have seen stuff saying it's not advisable to change the default group  permission level? Any advice gratefully received. 

Hello @Victoria Symons, may  I suggest the following ideas:

since SharePoint start 19 years it was always a good thing to have a low number of permission levels and level only for one group, not in several groups or even persons to deal with the items or documents.

 

Otherwise there will be permission chaos and you have lots of trouble because of single permissions on single persons for single items...

 

Also the modern SP sites are constructed with a better clarity with only 3 permissions levels on each new site, which is always connected with a team (an o365 group) or which is a private site in a Teams channel.

 

And if you need to have user-defined permission levels and groups you can create it on lists and libraries. The Sites will not accept it and I think this is a great structure now.

 

But these extra permission structures are complicating again and clarity will be lowered. 

 

Greets, Eva