06-27-2017 03:20 PM
06-27-2017 03:20 PM
I have been looking at Stream over the past few days and I have a question related to channel permissions and how they will migrate over to Stream.
Our current O365 Video offering relies on channels with 1 or more owners who manage the permissions on the channel (Owners, Editors,Viewers). Owners use AD groups or just individual O365 accounts to manage permissions.
From what I am seeing in Stream, a Channel can only use Office 365 Groups (Stream groups) to set permissions on the channel. We are in the process of planning for O365 Groups, but at this time we do not have many groups and it is highly unlikely that we will give users the ability to create O365 groups.
It seems that Stream has made an architectural decision based on the fact that everyone is fully implementing Office 365 Groups. Did I miss something?
Hoping @Marc Mroz is still monitoring this community.
06-27-2017 03:33 PM
Hey @Tim Crean!
We did take a architectural bet on O365 Groups. Since so many O365 services are doing this same thing, we needed to do something similiar so that we can easily do deeper integrations with them in the future (Teams, Yammer, SP, Outlook, StaffHub, etc) and have the same base set of permissions enforced.
This does mean that you are constrined to Owners/Members in a Group and can't nest securty groups.
However for migrating the channels from O365 Video to Stream, we are not going to be automatically making new O365 Groups for them. We'll have a "special" group type in Stream that will port over the owners/editors/viewers and all permissions (including security groups) from the O365 Video channel. This will allow us to have a 1 to 1 mapping of O365 Video channels to a group entity in Stream with exact permissions.
For Stream GA we decided to stick with just exposing the owners/member on the O365 Group in Stream to not make things complicated.
But when we do the migration we'll have a Stream group that is NOT connected to an o365 group. In the back of my mind I have a feeling that when we do this we might also need/want to allow creation of groups in Stream in this same way.
We haven't set this as the plan yet, but would love your and other customer's feedback after they've played with Stream to see if this is needed or not. I think we need you all to use Stream groups that are connected to O365 Groups for a while to see how it feels. If after using it for a while you feel you need a Stream group that's not connected to groups we can think about doing that, as technically under the covers we'll have the ability to do so.
06-27-2017 05:02 PM
07-03-2017 08:05 AM
07-10-2017 11:23 AM
That porting will be helpful but for sure the lack of support for Active Directory security groups will be a pain point for us. Especially for Viewing permissions when it is set to something less than "everyone" and more than "small group." e.g. "everyone in R&D business unit" - we don't have O365 Groups for those things and I suspect most orgs don't.
07-11-2017 11:05 AM
Thank you so much for the feedback everyone. We will definitely factor this into the thinking. Two things we will have for sure are
The feedback on this thread seems to indicate that we should allow creating these "Special" Stream groups for non migration scenarios too.
08-31-2017 05:25 PM
I had a chance to take Stream for a longer spin recently.
First off, What we like:
1. We like the concept of O365 Groups and we have an active project to understand and support Groups on campus. However, some of our departments are very deep into use of AD groups managed by Grouper and used (in some cases) as both mail enabled groups and as security groups. The reality is that most of those AD groups will never be migrated to an O365 Group, so it is very important that Stream have the ability to use those groups in a migrated channel, as well as with a new channel.
2. From what I can tell, Stream channels do not have the concept of Owner,Editor, Viewer when creating a new channel with an O365 Group. That permission structure in Video was one of the things we found very useful for our channel owners. It looks like there are now two levels: Owner and Editor. Is that correct? If so, how will the Owner,Editor, Viewer permissions be migrated from Video to Stream?
3. The Admin controls in Stream also appear to be a bit limited compared to what we are used to in Video. At the Stream Admin level, video upload and channel creation permissions are combined. In Video we have the ability to restrict channel creation to a group, but allow video upload at the channel level based on channel owner's needs. This seems very limited. Our vision for enterprise video did not involve allowing end users to create their own channels. In addition, at this point we do not allow O365 Group creation by our users. It is something we are exploring, but no decison as of yet.
4. Our Accessibility and Usability Lab has done some initial testing of Stream with screen readers, just as we did with O365 Video. I expect we will have some feedback based on their testing in the next couple of weeks. Can we reach out to you at that point, or do you have an alternate contact for Accessibility in Stream.
Thank you both for listening to all of the feedback and apologies for my delay in response.