Aug 04 2023 08:14 AM
My team manages a knowledge base that is used by our entire organization to share documentation on IT-related processes. We have been using Stream (Classic) to upload and share videos by embedding them into the KB articles, so we could take advantage of the view analytics and autogenerated captions. I created a channel and set the access permissions so anyone the org could access it.
Now we are being pushed over to the new version of Stream, which doesn't have a channel feature (that I can see, anyway), and so we've been manually setting the access for each video before creating the embed code. But we recently discovered that people are not able to view these videos because they are getting a permissions error, saying that they need to request access. We tried putting videos inside a folder that had permissions set to viewable by anyone in the org, so that files would inherit the permissions, but that didn't work either.
Please help us figure this out! We'd love to keep using Stream, but won't be able to if we can't fix this issue.
Aug 08 2023 03:26 AM
@JoelAndrews I have exactly the same issue - have managed to get an embed code working that doesn't need them to request access by using the share to group - viewable to all in org link, and changing the embed link to that.
But, using that shows a tool bar at the top, for uploaind and creating videos which I really don't want,,,
Aug 22 2023 08:49 AM - edited Aug 22 2023 08:50 AM
Following this post - I'm interested on the topic too 🙂
Aug 22 2023 11:35 AM
SolutionJust following up on this. The solution that I eventually arrived at was to move the files to the document library of a public (within org) SharePoint site. Once I did that, people were able to view the videos via Stream. I still don't understand why we couldn't do this within the other site's library simply by manually setting the folder permissions to anyone in the org. That used to work, but maybe something changed so that now the permissions of the site overrides any manually set permissions within.
Aug 22 2023 11:42 AM
Aug 29 2023 01:42 AM
@JoelAndrews I ended doing something similar - moved the files to a sharepoint, and changed the folder settings there to everyone in org can view etc.
Since the sharepoint is linked to a team, does make it simpler for our video creators - they just drop the file in the correct folder in MS Teams - click on it - grab the embed code, and it'll work.
Aug 22 2023 11:35 AM
SolutionJust following up on this. The solution that I eventually arrived at was to move the files to the document library of a public (within org) SharePoint site. Once I did that, people were able to view the videos via Stream. I still don't understand why we couldn't do this within the other site's library simply by manually setting the folder permissions to anyone in the org. That used to work, but maybe something changed so that now the permissions of the site overrides any manually set permissions within.