Forum Discussion
Changes to meeting recordings - saved to OneDrive and SharePoint instead of Stream.
- Oct 05, 2020
EmileRec Hello! I haven't had a chance to try this so I can't say anything about the inheritance and if they can actually delete the recording. But it's a good question and the official docs aren't clear about it.
In your scenario you're using a channel meeting and permissions are inherited from the owners and members list in the channel as per this description.
Who has the permissions to view the meeting recording?
- For non-Channel meetings, all meeting invitees, except for external users, will automatically get a personally shared link. External users will need to be explicitly added to the shared list by the meeting organizer or the person who started the meeting recording.
- For Channel meetings, permissions are inherited from the owners and members list in the channel.
https://docs.microsoft.com/en-us/MicrosoftTeams/tmr-meeting-recording-change#frequently-asked-questions
Then you have a couple of disclaimers saying:
- "Only the organizer of the meeting (non-channel) and the person who started the recording will be able to edit the recording. But everyone invited to the meeting will be able to view the recording."
- "In Q1 of 2021, only the meeting recorder and organizer will be able to download the meeting recording. All other attendees will only be able to view it."
https://support.microsoft.com/en-us/office/play-and-share-a-meeting-recording-in-teams-7d7e5dc5-9ae4-4b94-8589-27496037e8fa#bkmk_meetingrecordingstorage
So I suppose you have to edit the permissions when recording a channel meeting (SharePoint) as the permissions are inherited. At least for now.
natpascual1330 Hi, the permissions follow the meeting type and who clicked on record. The storage location also depends on this https://docs.microsoft.com/en-us/microsoftteams/tmr-meeting-recording-change#permissions-or-role-based-access
If all seems to be OK but still get the error message you might be better of creating a support ticket with Microsoft. If you're not an admin yourself reach out to your IT admin to get help with that.
Noted on that. Here's another set of screenshots based on the permissions. Which is weird, it says it's shared with me (Nat Pascual), but if I check my permission, it says The user might not be able to access the item. But, at the bottom it says I have Read permissions. Am I understanding my having Read permissions wrong?
- Ian CockburnFeb 24, 2021Copper Contributor
natpascual1330 I think I may have hit the same issue you are having with permissions. Did you get this resolved?
- JordanPowerFeb 26, 2021Copper Contributor
Ian Cockburn - Encountered similar issue with a user today. A non-channel meeting was recorded and stored in the recorder's OneDrive and a shared link was generated and sent to the Teams chat. One user got access denied when trying to view the file. Confirmed w/ the recorder that the user was listed and they also tried sharing the "Copy Link" URL, but still no luck.
While troubleshooting with the user, I noticed the recording displayed under the Recent documents section on the https://office.com page. Lo and behold, the video worked just fine from here! The URL was to the recorder's OneDrive site, but the video was playing in the built-in browser video player - not the SharePoint/OneDrive video player. So the user does in fact have access to the file, it's just the underlying application page that the normal shared link is trying to load with the video embedded in that they likely aren't getting proper access to.
- Ian CockburnFeb 26, 2021Copper Contributor
- ChristianBergstromFeb 04, 2021Silver Contributor
natpascual1330 Hello, when you record a non-channel meeting the recording end up in OneDrive, depending on meeting type and who clicked on record the location and permissions will differ. When you record a channel meeting the recording end up in SharePoint (permissions are inherited). So compare the table with what you're doing. If it doesn't work as intended I suggest opening a support ticket with Microsoft.