Enable Admins to manage the creation of new groups.
It is unbelievable to us that at Yammer's current level of product maturity, that our Admins cannot control the creation of new groups. This severely limits the platform as an effective collaborative platform.
Allowing everyone to create a group, or write a post, on Yammer are core to our product philosophy that everyone in an org should be empowered to communicate.
To vote for this please see --https://yammer.uservoice.com/forums/399627-yammer/suggestions/18966958-admins-to-approve-yammer-groups
This is a very simple easy fix. Just hide the "Create a group" link; let the company decide for themselves if they want to expose this link to everyone or only to the admin.
Björn Elwhagen commented
The fact that you have disabled the voting for this when you 7 times more comments than votes is just strange. Why would you restrict your users from giving you feedback on this in the form of voting? Obviously your users want this feature. Do you actually think that you know better than your users what is good for their organization?
Rob Christensen commented
The response that "we're unlikely ever to build this" is not acceptable.
Everyone agrees with the philosophy "that everyone in an org should be empowered to communicate", but that does not mean you have no governance around the product.
In an enterprise environment, basic governance to allow for better communication (as well as compliance and resource consumption (in O365 groups)) is a must. Sprawling, ungoverned groups do not allow for good communication, in fact it can cause the opposite where users are confused and overloaded of where and when to communicate. Providing a workflow and governance process around group creation would only setup Yammer to be more successful, not less.
We need to be able to manage group creation. My list of groups looks like is a mess!
Nick Hurst commented
There is a similar uservoice idea that can still be voted on:
Nick Hurst commented
Not only will Microsoft not listen to their customers, but they block us from even voting on this feature.
I thought the 'new Microsoft' was supposed to listen to their customers? This seems like the old Microsoft that we have all experienced throughout the years. Where they think they know what's best for millions of customers throughout countless industries and aren't interested in hearing otherwise.
We have empowered our users to communicate through Teams and Email, we need controls as Yammer would only have a limited use case in our organization. As it currently stands, without admin controls we just aren't going to allow anyone to use Yammer. Is that your goal?
Victoria D'Apice-Loh commented
This is a mistake, it should be up to the individual network as to how it should be managed. Our members blatantly disregard policy, messaging, standards, best practices, and create redundant groups, inappropriate group, unlist/hide inappropriate groups, and have clearly said "if I have the option I'm doing whatever I want"making it impossible to keep the network healthy and secure.
We need this functionnality, without it will be chaos....
In O365 Groups, we only authorise admins to create groups to ensure we have a proper naming convention, that owners are trained... We are a group of 50000 Employees.
In Yammer, we will setup the integration with O365 groups: by allowing anybody to create Yammer groups, the O365 groups created automatically will not follow our naming convention creating potentially thousands of O365 Groups, SP Sites, Exchange mailboxes automatically.
We need to have the possibility in Yammer to restrict group creation.
I dont think we are disagreeing with the product philosophy "that everyone in an org should be empowered to communicate" we are asking for an ability to manage how this is done. It's not really Microsoft's place to decide this. We restrict access to a number of different products based on the level of employee and how our business is structured.
Although, not entirely sure Yammer even use this platform (or listen to feedback) anymore
James Emanuelli commented
Disabling yammer until this is available, otherwise throwaway groups will be started up and data thrown about and users will complain they can't find anything. Would be fine if it was just a BB but the fact it spawns 365 groups and stores files means its just unworkable.
Blaine Holt commented
Restrict users from creating groups in Yammer. As a company we really want all the comments to be in the groups that we control. Would you please add the feature as soon as possible. I have seen many other users on different tech sites complaining about the same issue. This would help us greatly.
Jason Strudwick commented
Our school district will not be providing Yammer to students without the ability to restrict creation of groups. It will be provided as an option for teachers to collaborate only.
It is standard practice in our K-12 educational environment that by default a designated leader facilitates the collaboration in a manner appropriate for the students. In the higher grades quite possibly it could be opened up, if the principal feels it is appropriate for their environment.
By taking away our option to choose and mandating the product philosophy, "everyone in an org should be empowered to communicate", you are restricting our environment from adopting this product for students.
I agree that everyone should be empowered to communicate, sometimes they need a little assistance to remain focused in the delivery.
As a school, this philosophy has meant that we have had to close down Yammer due to misuse. It would have been a useful discussion board tool otherwise.
Perhaps your core philosophy is only suited to a portion of your market. Is there an office 365 app aimed at schools which would allow a controlled discussion?
I don't think this makes much sense. Office 365 enables the creation of Office 365 groups to be restricted. However with Yammer, an ordinary user can create a Yammer groups and convert it to an Office 365 group by simply including one of the restricted accounts.
I get that restricting group creation might not suit every user but it is clearly useful in some cases and (as per the above example) doesn't fit well with the existing security model for Office 365 groups.
Joe Mallen commented
I don't believe that Microsoft should make decisions on how we empower our users. The creation of groups will simply get out of control and you will have several conversations on the same topic in different groups and impossible to manage. We will lose content and the organization will simply not be organized with groups created with no controls. Please reconsider allowing only admins to create groups. Just like we don't allow folks to create their own distro emails.
I also agrre with this functionality. A corporate need to control a minima the external group creation by the admin.
Stu Hasic commented
Once Yammer has been established in an organization with many users and groups, new users that join the organization should not be able to create a group until they have participated in Yammer effectively. It's not helpful that as part of the sign-up process that one of the first steps presented to the new user includes "Create a New Group". Typically these people have no idea what they are doing and we end up with duplicate or pointless groups administered by novices. It's not conducive to an effective community. New users should all be required to either create a certain number of new posts in groups or reply to a certain number of existing posts before they should be able to see the "Create a New Group" option. Let's say it's 10 posts as a minimum. Maybe then they can be given a popup that says "you've now earned the ability to create and manage a group that you think is missing from Yammer!"
I think this would help manage the number of stupid and duplicate groups that are created and reward new users following valued participation. Group Administration should not be available to a newcomer.
I understand that this is not workable in the early stages of setting up a Yammer community where groups need to be created by newcomers, but maybe Yammer Admins should only get that option to start with. Happy if this gets fleshed out in this discussion.