Forum Discussion
In public preview: Meeting co-organizer
- Mar 10, 2022
Currently, the co-organizer feature doesn't support breakout rooms. Here is a temporary workaround for adding your Co-Organzier as a Breakout Room Manager, until it's fully supported:
BEFORE A MEETING
-
Organizer creates meeting
-
Organizer opens the meeting on their Teams calendar & adds Breakout Rooms (BR) to it
-
BRs shows up as a new tab along with other apps added to the meeting
-
Organizer then uses BR app's settings to assign a person invited to the meeting as a BR manager
-
Organizer opens meeting options and assigns meeting co-organizer role to that same person
DURING MEETING
-
Imagine that organizer is out of office that day (like in a substitute teacher scenario)
-
The co-organizer joins the meeting & they have all the capabilities of co-organizer role
-
The co-organizer starts the BR in the meeting
-
When co-organizer joins the BR, they no longer have the co-organizer role but since that person was assigned as a BR manager, they can manage the BR with all capabilities of a BR manager (their role essentially changed from "co-organizer" to "BR manager")
-
Once BR session is over, BR manager & other attendees will leave the BR and rejoin the main meeting
-
When they rejoin the main meeting, everyone is automatically assigned their original meeting roles for the main meeting
-
So, the original co-organizer who filled the BR manager role during the breakout room session automatically becomes a co-organizer in the main meeting once again
-
We have several meetings that at some point were created by separate users. It would be nice if co-organizers could adjust the meeting invitation list - or in our case have ALL the abilities of a standard organizer.
Having to message an organizer to edit the invitations for multiple meetings with users coming and going can be a chore - you then have to rely on the organizer to make the change in a timely manner as well.
- GeorgVAug 19, 2022Brass Contributor
MS basically built a car and forgot to put the wheels on it. I am confronted with several large events where one colleague left the company and another is on parental leave. Is the solution to setup new Webinars and put all attendees through re-registration or embarrassing "look we cannot sort our stuff" procedure? Or shall we break law and I use their logins? Seriously.
Can someone from the product team please state what the agenda here is?
If nothing happens, it is turning back to GoTo or Zoom.
Please vote on feedback: https://feedbackportal.microsoft.com/feedback/idea/22dd7159-f00b-ed11-a81b-6045bd7d68ae#comments
- rccryanAug 19, 2022Copper Contributor
GeorgV, honestly, I wouldn't recommend waiting around for a fix on this. While I have nothing against MS or Teams, there are two key problems with it:
1) MS has to keep Teams integrated with the rest of the MS Office ecosystem and this adds complexity, security considerations, etc. that drastically slow its development and also make it overly complicated for the users.
2) for most of us, Teams is an added feature that comes along with the products we intended to purchase (Word, Excel, Outlook, One Drive, etc.), so it doesn't much matter to most people how well it works or which features it has. While MS does offer a Teams stand-alone license or two, I doubt these are used by very many people given the superiority of the competition (plus they are comparatively cheap and everyone knows you get what you pay for). Therefore, out of the many, many users of Teams (both regular and occasional), relatively few will complain or provide meaningful feedback and nobody is going to cancel their MS Office license simply because of a Teams problem. Thus, there is little economic incentive for rapid, high quality development.
While it would be nice to be able to use Teams instead of Zoom since it's already "paid for", we didn't have the luxury, patience, or base technical ability to navigate all the workarounds required to make it functional and practical. - GeorgVAug 19, 2022Brass ContributorEmily Kirby -- sorry, but this feedback should not have been closed. It is missing the critical ingredient: https://feedbackportal.microsoft.com/feedback/idea/0bf64469-bf99-ec11-b401-002248312dc8