Forum Discussion
Solved
Channels not visible for private group videos view-able by all
Although I am still grappling with the permissions architecture and groups dependency in Stream for long, I recently gave it a try. Use case: Our internal communications team has several vide...
Abhimanyu Singh - You are right your only options are a new or existing public O365 Group to accomplish most of what you want.
The setting in Stream for making members viewers only, does only apply to Stream not to the other workloads that come with the O365 Group.
With your use case and scenario you can't quite get all the requirements covered. We are going to be doing more research and customer interviews in this new year to come up with plans on how to better address Stream groups/channels/permissions. We may want to reach out to you (and others who are interested) as we start our interviews in the coming weeks.
Tomislav Karafilov thank you for helping out. Much appreciated.
Now that leaves me with two options:
1. Make this group public. That will violate requirement #3 of the use case. Any user will then be able to join the group and hence access other workloads (site, planner, teams, etc.)
2. Create a new public group. That means a new name, duplication of all workloads, and then the end users (especially the communications team) get all confused and mixed up with what goes where and how!
Which is the lesser evil? I wish someone from Microsoft could state that there is another option which is not evil? Ever since O365 Groups concept got launched, I am finding myself in one conundrum or the other every day! 😞 So much for modern!
Marc Mroz
Microsoft
MicrosoftAbhimanyu Singh - You are right your only options are a new or existing public O365 Group to accomplish most of what you want.
The setting in Stream for making members viewers only, does only apply to Stream not to the other workloads that come with the O365 Group.
With your use case and scenario you can't quite get all the requirements covered. We are going to be doing more research and customer interviews in this new year to come up with plans on how to better address Stream groups/channels/permissions. We may want to reach out to you (and others who are interested) as we start our interviews in the coming weeks.
Marc Mroz thank you for the confirmation. I think we shall continue to stick to dumping videos in a document library for now. Stream as it stands today, doesn't provide any value to us. With Microsoft removing the feature of extracting EXIF/metadata data into columns, and unavailability metadata/columns in Stream; things are already getting more and more constrained.
I would certainly like to participate in the interviews that you are planning. Please count me in. Hoping that would help make Stream useful to our use-case(s).
Somehow, I strongly feel that using O365 Groups as the underpinning for permissions is the root cause of such usability problems not only with Stream but other workloads as well. O365 Groups as a membership construct is great, but as a permission model needs serious re-think.