# Documentation for OAuth Scopes **URL:** \ **Category:** API and Webhooks\ **Created:** [December 11, 2018, 12:15am UTC](https://devforum.zoom.us/t/documentation-for-oauth-scopes/2691 "2018-12-11T00:15:02Z")\ **Posts on this page:** 7\ **Page:** 1
**Author:** ![jeff](https://sea2.discourse-cdn.com/flex016/user_avatar/devforum.zoom.us/jeff/32/121_2.png) [@jeff](https://devforum.zoom.us/u/jeff)\ **Post date:** [December 11, 2018, 12:15am UTC](https://devforum.zoom.us/t/documentation-for-oauth-scopes/2691/1 "2018-12-11T00:15:02Z")
Hi folks, I cannot find any documentation for the OAuth scopes that you support. Specifically, I am looking for - an explanation of what scopes like `meeting:write user:read recording:write webinar:write` do - discussion of whether it is possible to request different scopes other than all of the above (either a subset thereof, or others not listed) - explanation of whether these scopes permit the authenticated user to manage their data alone, or that of their whole company (i.e. other users at their domain who are also using Zoom) This documentation might look like [this](https://api.slack.com/docs/oauth-scopes) (but for your API). ---
**Author:** ![TimZoom](https://sea2.discourse-cdn.com/flex016/user_avatar/devforum.zoom.us/timzoom/32/978_2.png) [@TimZoom](https://devforum.zoom.us/u/TimZoom)\ **Post date:** [December 11, 2018, 11:23pm UTC](https://devforum.zoom.us/t/documentation-for-oauth-scopes/2691/2 "2018-12-11T23:23:08Z")
On each API we list the scopes in the description section. Does this solve your requirement or do you need a more high-level? ---
**Author:** ![jeff](https://sea2.discourse-cdn.com/flex016/user_avatar/devforum.zoom.us/jeff/32/121_2.png) [@jeff](https://devforum.zoom.us/u/jeff)\ **Post date:** [December 11, 2018, 11:50pm UTC](https://devforum.zoom.us/t/documentation-for-oauth-scopes/2691/3 "2018-12-11T23:50:24Z")
Thanks for your reply Tim. When you write > On each API we list the scopes in the description section where can I find this? For example, if I visit [Zoom API](https://zoom.github.io/api/#create-a-meeting), I assume that that API requires the `meeting:write` scope but I don’t find that discussed anywhere on the page. ---
**Author:** ![michael\_p.zoom](https://sea2.discourse-cdn.com/flex016/user_avatar/devforum.zoom.us/michael_p.zoom/32/18105_2.png) [@michael\_p.zoom](https://devforum.zoom.us/u/michael_p.zoom)\ **Post date:** [December 17, 2018, 8:08pm UTC](https://devforum.zoom.us/t/documentation-for-oauth-scopes/2691/4 "2018-12-17T20:08:19Z")
Hi @jeff, We have a new API reference page, please refer here - [https://marketplace.zoom.us/docs/api-reference/zoom-api/meetings/meetingcreate](https://marketplace.zoom.us/docs/api-reference/zoom-api/meetings/meetingcreate) ---
**Author:** ![jeff](https://sea2.discourse-cdn.com/flex016/user_avatar/devforum.zoom.us/jeff/32/121_2.png) [@jeff](https://devforum.zoom.us/u/jeff)\ **Post date:** [December 17, 2018, 10:12pm UTC](https://devforum.zoom.us/t/documentation-for-oauth-scopes/2691/5 "2018-12-17T22:12:09Z")
@michael_p.zoom, thanks for your reply. I see that that page states that `POST /users/{userId}/meetings` requires the `user:write:admin user:write` scopes. However that still does not help me answer my questions: - what do those scopes do (what resources do they allow access to)? I wish to know this for _all scopes_ because you have multiple; in particular our tokens have the scopes `meeting:write user:read recording:write webinar:write`. - is it possible to request different scopes to use `POST /users/{userId}/meetings`? I suspect the answer is _yes_, because our access tokens do not have the scopes given [here](https://marketplace.zoom.us/docs/api-reference/zoom-api/meetings/meetingcreate)—rather they have the scopes `meeting:write user:read recording:write webinar:write`—and we are still able to use that API. - do any of the scopes above permit the authenticated user to manage their data alone, or that of their whole company (i.e. other users at their domain who are also using Zoom) - if any of the scopes above permit the authenticated user to manage the whole company’s data, are there equivalent scopes (for purposes of using `POST /users/{userId}/meetings` and `PATCH /meetings/{meetingId}`) that only allow the user to manage their individual data? I would be much obliged if you would answer those questions directly, without reference to further documentation pages, unless those pages definitely have answers to those questions. Thanks. ---
**Author:** ![TimZoom](https://sea2.discourse-cdn.com/flex016/user_avatar/devforum.zoom.us/timzoom/32/978_2.png) [@TimZoom](https://devforum.zoom.us/u/TimZoom)\ **Post date:** [January 2, 2019, 4:32pm UTC](https://devforum.zoom.us/t/documentation-for-oauth-scopes/2691/6 "2019-01-02T16:32:22Z")
Hey Jeff, I have been out on vacation sorry for the late response. So, our scopes have two “types” there are user level scopes and account level scopes. User-level scopes are the ones you are mentioning above. Account level scopes however will have `:admin` appended to the scope. These are the scopes that allow data manipulation for other accounts. So, in your case these scopes will only be able to manipulate the data associated with the account. The rest of the scope “forumla” is pretty straight forward. `webinar:write` for isntance could create webinars and `webinar:read` can read webinar info from the account. ---
**Author:** ![jeff](https://sea2.discourse-cdn.com/flex016/user_avatar/devforum.zoom.us/jeff/32/121_2.png) [@jeff](https://devforum.zoom.us/u/jeff)\ **Post date:** [January 2, 2019, 7:19pm UTC](https://devforum.zoom.us/t/documentation-for-oauth-scopes/2691/7 "2019-01-02T19:19:50Z")
@TimZoom, that answers all my questions. Thanks!