Jun 17 2020 11:30 AM
The New Yammer experience allows for the ability to restrict who can post in All Company. e.g. Admins can post corporate content and users can reply, similar to an employee communications newsfeed. However, this could be viewed as taking away employees' ability to share and/or collaborate in All Company with all users, which they've been accustomed to thus far.
Is there any case studies best practices or pros and cons on All Company Community Newsfeed (restricted) vs. All Company Communities (Unrestricted)?
Could we have both?
Jun 21 2020 09:02 AM
@andrewclarke It definitely can't be both.
It's always been the case that the best experience in Yammer has been in groups/communities, to help align the topics for conversations. With All Company kind of being a "not sure where to post" last resort. A smaller number of Yammer networks have employed all company for "everyone in the company" announcements.
How you use it depends on the use case for your org. Do you want to restrict access to All Company only to admins to post? If so, is there another community where all users are added to (e.g. company watercooler) to fill the "not sure where to post" use case?
Jun 22 2020 02:24 PM - edited Jun 22 2020 02:25 PM
Thanks, Kevin. I appreciate your response. Currently, all employees are added to the All Company community by default. Do you know if it's possible to add all employees into two communities? For example: 1: All Company Restricted; and, 2) All Company Unrestricted "Watercooler"
Jun 22 2020 02:29 PM
@andrewclarke Yes, you can make any Office365/M365 Group have a query from Azure AD to auto-add all your employees to the group.
Jul 16 2020 04:11 PM
Jul 16 2020 05:07 PM
@andrewclarke With dynamic groups there if you set up a rule to add all employees to a Yammer community then there is no way for them to leave.
https://docs.microsoft.com/en-us/azure/active-directory/users-groups-roles/groups-dynamic-membership
https://docs.microsoft.com/en-us/yammer/manage-yammer-groups/create-a-dynamic-group