We are trying to setup an OAuth app on Zoom Marketplace for internal purposes, one of the requirements from the customer is to capture back the recording done as part of the meeting.
While checking the Features section, to track the event “Meeting Recording Completed”, we need “recording:read:admin” scope.
Our internal security is not happy with the application having this role since, it might be used to fetch confidential recording and several other legal issues.
Is there any recommendation from Zoom to overcome this? Or any documentation on how the callbacks work with an architecture diagram will help us in justifying having this OAuth scope for our app.