Add moderated public team (request to join) as an option besides public and private
It would be good to have a third option when creating a team besides 'private' and 'public'.
Private means member editor access only, but also makes the team not discoverable for interested people who are not a member, and then could request to join.
Public means the team and it's content is open to anyone on the tenant.
For organisations with specific BU's who would like to be discoverable for non-team membersb(thus needs to be public), but only allow memership (join) after a request (moderated membership).
There could actually be 2 types of moderated teams:
1. Public and moderated where only team name an description is discoverable, but content cannot be seen.
2. Public and moderated where the contentcan also be viewed without being a member.
Membership then always means being able to contribute, not just read/view.
Sasja Beerendonk
shared this idea
5 comments
-
Lydia
commented
A Much needed feature would save a lot of duplication. I am boggled this doesn't already exist
-
Anonymous
commented
Would also more follow the SharePoint model. Public means everyone can read and join. Public Moderated would mean everyone can read and you can join when an onwer approves membership. In any case, only members should be able to modify.
-
Jonathan
commented
This is a much needed feature. I would also suggest just adding Internal as a third Class Type. A Team created with class type Internal suggests by default the Team is discoverable within your Tenant -- allows end-users to see Display Name, Description and Owners to determine if they want to submit a request to join. Data Classification labels could be used to filter out any Internal Teams from being discovered (as needed).
-
Anonymous
commented
This is a huge need! In an EDU tenant we have so many different scopes to our user population. We want to promote the ability for users to collaborate through their own discovery of teams. Additionally remove the management of team membership which currently forces owners to know of others who should be members or to review membership lists if join with a code is used to remove those who may not have supposed to have joined.
-
Bas Boss
commented
Excellent suggestion.
In our experience a lot of duplicate teams are being created because employees simply didn't know the team already existed.
It would give our employees a great way to see what's going on in our organisation and who's working on what.