# Zoom OAuth App Selection Missing Granular Scope Options **URL:** \ **Category:** API and Webhooks\ **Created:** [September 13, 2024, 7:24pm UTC](https://devforum.zoom.us/t/zoom-oauth-app-selection-missing-granular-scope-options/117452 "2024-09-13T19:24:41Z")\ **Posts on this page:** 7\ **Page:** 1
**Author:** ![amp23](https://sea2.discourse-cdn.com/flex016/user_avatar/devforum.zoom.us/amp23/32/52452_2.png) [@amp23](https://devforum.zoom.us/u/amp23)\ **Post date:** [September 13, 2024, 7:24pm UTC](https://devforum.zoom.us/t/zoom-oauth-app-selection-missing-granular-scope-options/117452/1 "2024-09-13T19:24:41Z")
I’m trying to make requests to the following Zoom API endpoints: - `/report/activities ` - `/report/operationLogs` To view: Zoom Meeting API: Sign In/Sign Out Activities Zoom Meeting API: Operation Logs However, I’m encountering this error: `Request is unable to be processed at this time due to No permission.` The documentation mentions that specific granular scopes are needed, but I don’t see these scopes listed under the `Report` section in the Zoom app settings. I’ve already confirmed that my app has the `report:read-admin` scope, but I don’t see an option to add the necessary granular scopes. We previously had the granular scopes, but I’m not seeing them any longer and am wondering what happened or what scopes we should be using instead? When I click `Add Scopes > Product > Report` I see: `report:master` `report:read:admin` and `report_chat:read:admin`. Additionally, we’re hitting these API’s using an enterprise account. How can I add these granular scopes to the app or did something about these API’s change? We appreciate your help. Thanks! ---
**Author:** ![amp23](https://sea2.discourse-cdn.com/flex016/user_avatar/devforum.zoom.us/amp23/32/52452_2.png) [@amp23](https://devforum.zoom.us/u/amp23)\ **Post date:** [September 19, 2024, 4:27pm UTC](https://devforum.zoom.us/t/zoom-oauth-app-selection-missing-granular-scope-options/117452/2 "2024-09-19T16:27:52Z")
Hi @gianni.zoom, I noticed you assisted another customer with a similar issue titled " Granular Scopes Not Appearing" and I was hoping you could take a look at this one as well. (I’m unable to add the link). We’re encountering permission errors due to missing scopes, but there’s no option to set them. Any guidance you could provide would be greatly appreciated. Thanks so much! ---
**Author:** ![gianni.zoom](https://sea2.discourse-cdn.com/flex016/user_avatar/devforum.zoom.us/gianni.zoom/32/32523_2.png) [@gianni.zoom](https://devforum.zoom.us/u/gianni.zoom)\ **Post date:** [September 20, 2024, 2:40pm UTC](https://devforum.zoom.us/t/zoom-oauth-app-selection-missing-granular-scope-options/117452/3 "2024-09-20T14:40:47Z")
Hi @amp23 , I just responded to you and I’ll link it here for anyone else in your specific situation. > [@Granular Scopes Not Appearing](https://devforum.zoom.us/t/granular-scopes-not-appearing/110556/33): > > Hi @amp23 , what app type is this? S2S or general OAuth? This is unexpected. Can you recall around when you noticed this change? If you have any evidence to support seeing the switch from granular back to legacy scopes that would be helpful. Additionally, I’m going to private message you directly for the following: dev email client id for app screenshots of scope you’re seeing API response zm-tracking-id from API response header ---
**Author:** ![amp23](https://sea2.discourse-cdn.com/flex016/user_avatar/devforum.zoom.us/amp23/32/52452_2.png) [@amp23](https://devforum.zoom.us/u/amp23)\ **Post date:** [September 26, 2024, 2:15pm UTC](https://devforum.zoom.us/t/zoom-oauth-app-selection-missing-granular-scope-options/117452/4 "2024-09-26T14:15:16Z")
@elisa.zoom I believe you helped me with the initial configuration and am curious if you know what happened to the granular scopes for the OAuth App? Thanks! ---
**Author:** ![gianni.zoom](https://sea2.discourse-cdn.com/flex016/user_avatar/devforum.zoom.us/gianni.zoom/32/32523_2.png) [@gianni.zoom](https://devforum.zoom.us/u/gianni.zoom)\ **Post date:** [September 26, 2024, 3:13pm UTC](https://devforum.zoom.us/t/zoom-oauth-app-selection-missing-granular-scope-options/117452/5 "2024-09-26T15:13:25Z")
Hi @amp23 just responded to you in the private message. ---
**Author:** ![amp23](https://sea2.discourse-cdn.com/flex016/user_avatar/devforum.zoom.us/amp23/32/52452_2.png) [@amp23](https://devforum.zoom.us/u/amp23)\ **Post date:** [October 8, 2024, 5:03pm UTC](https://devforum.zoom.us/t/zoom-oauth-app-selection-missing-granular-scope-options/117452/6 "2024-10-08T17:03:57Z")
I was able to resolve this by filing a support ticket [here](https://support.zoom.com/hc/en?id=home) and was helped by @elisa.zoom. Posting what I learned in case it helps someone else in the future. The behavior I was experiencing is expected. Zoom transitioned from Classic Scopes to Granular Scopes in March. If you have an existing app using Classic Scopes, they will remain compatible, but it’s recommended to upgrade through the migration process in your OAuth application. To do so, you’ll need to create a new application. Additionally, any time you add a new scope, users will need to reauthorize. If you create a new app, the app must undergo the functional review process again. Granular Scopes are not available for classic apps. I also encountered “no permission” errors from the Zoom API. In this case, ensure that the user authenticating has met the prerequisites outlined in the support section linked in the API documentation. Support reference: [Zoom Support Article](https://support.zoom.com/hc/en/article?id=zm_kb&sysparm_article=KB0060623) API Documentation: [Zoom OAuth Scopes](https://developers.zoom.us/docs/internal-apps/oauth-scopes/) ---
**Author:** ![system](https://us1.discourse-cdn.com/flex016/uploads/zoomdeveloper/original/3X/6/1/614bdd549b610bbaa46ff934617683a02bdaa03c.png) [@system](https://devforum.zoom.us/u/system)\ **Post date:** [October 9, 2024, 5:04pm UTC](https://devforum.zoom.us/t/zoom-oauth-app-selection-missing-granular-scope-options/117452/7 "2024-10-09T17:04:29Z")
This topic was automatically closed 24 hours after the last reply. New replies are no longer allowed.