Why do you need these Zoom scopes for?

Created by Tim Kefford, Modified on Tue, 24 Mar at 11:51 AM by Tim Kefford

When setting up your Zoom account within our platform, you are provided a list of scopes (permissions) that you need to approve before you can integrate your service. This article provides further explanation and links to the official Zoom documentation, so you can gain a complete understanding.


Further reading: https://developers.zoom.us/docs/integrations/oauth-scopes-granular/


ScopeDescriptionWhy Morbit Studio Requires It
Accounts
dashboard:read:meeting:adminView a meeting's metricsRetrieves per-meeting metrics (packet loss, jitter, latency, bitrate) for call quality reporting within Morbit Studio.
account:read:account_setting:adminView an account's settingsReads account-level configuration to validate tenant setup and support multi-tenant deployments.
dashboard:read:list_meeting_participants:adminView meeting participants' metricsRetrieves participant-level metrics (device type, network performance) for meeting quality analysis.
dashboard:read:list_meeting_participants_qos:adminView meeting participants' quality of serviceRetrieves per-participant QoS data including MOS scores, packet loss, jitter, and latency for detailed call health reporting.
Dashboard
dashboard:read:zoomroom:adminView a Zoom Room's metricsRetrieves individual Zoom Room health detail, active issues, and live performance data for room-level monitoring.
dashboard:read:list_meetings:adminView meetings metricsLists meetings with participant counts and quality scores for reporting on meeting activity across the account.
dashboard:read:issues_zoomroom:adminView Zoom Room issuesRetrieves active and historical room issues and alert history to support IT helpdesk and fault monitoring.
dashboard:read:list_zoomrooms:adminView Zoom Room metricsLists all Zoom Rooms with live status, health scores, and peripheral health for the Morbit Studio room dashboard.
Meetings
meeting:read:meeting:adminView a meetingReads individual meeting details (topic, host, scheduled times) to enrich call quality records.
meeting:read:past_meeting:adminView a past meetingRetrieves historical meeting data for retrospective reporting and call quality trend analysis.
meeting:read:list_past_participants:adminView a past meeting's participantsLists participants from completed meetings to support historical QoS reporting and troubleshooting.
Rooms
zoom_rooms:read:room:adminView a Zoom RoomReads individual room details including display name, settings, and configuration for room inventory management.
zoom_rooms:read:alert:adminView a Zoom Room's alertReads active alerts on individual Zoom Rooms to surface device health warnings within Morbit Studio.
zoom_rooms:read:list_devices:adminView Zoom Room devicesLists hardware devices assigned to each Zoom Room, including make, model, serial number, and firmware version.
zoom_rooms:read:list_locations:adminView Zoom Room location hierarchy's locationsRetrieves the location hierarchy (country, region, city, building, floor) to organise rooms by physical location in Morbit Studio.
zoom_rooms:read:list_rooms:adminView Zoom RoomsLists all Zoom Rooms across the account, providing the primary room inventory used throughout Morbit Studio.
User
user:read:user:adminView a userReads individual user profile data (name, email, role) for mapping meeting participants to user records.
user:read:presence_status:adminView a user's presence statusRetrieves real-time user presence (Available, In a Meeting, Do Not Disturb, etc.) for display in Morbit Studio.
user:read:list_users:adminView usersLists all users on the Zoom account to populate and maintain user data within Morbit Studio.


Note: All scopes are read-only. Morbit Studio does not write any data back to Zoom. All data retrieved is used solely to display room status, device health, call quality metrics, and user presence information within the Morbit Studio platform for IT and operations monitoring purposes. 

Was this article helpful?

That’s Great!

Thank you for your feedback

Sorry! We couldn't be helpful

Thank you for your feedback

Let us know how can we improve this article!

Select at least one of the reasons
CAPTCHA verification is required.

Feedback sent

We appreciate your effort and will try to fix the article