# JWT for different scopes

**URL:** <https://devforum.zoom.us/t/jwt-for-different-scopes/42381>\
**Category:** Feature Requests\
**Created:** [February 3, 2021, 12:17am UTC](https://devforum.zoom.us/t/jwt-for-different-scopes/42381 "2021-02-03T00:17:52Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![matthew.h.barr](https://sea2.discourse-cdn.com/flex016/user_avatar/devforum.zoom.us/matthew.h.barr/32/19041_2.png) [@matthew.h.barr](https://devforum.zoom.us/u/matthew.h.barr)\
**Post date:** [February 3, 2021, 12:17am UTC](https://devforum.zoom.us/t/jwt-for-different-scopes/42381/1 "2021-02-03T00:17:52Z")

</div>

**Is your feature request related to a problem? Please describe.**  
JWT token auth is only supported on a single set of secrets for the entire account, at the admin level.

**Describe the solution you’d like**  
We would like to use JWT auth for a server side process that is scoped to much smaller access, potentially as far as a single user level.

**Describe alternatives you’ve considered**  
OAuth user level token renewals. It’s working, but was significantly harder to deal with and requires storing auth tokens and renewal tokens, even with a stateless/ server less app.

---

<div class="post-metadata">

**Author:** ![rgoh](https://sea2.discourse-cdn.com/flex016/user_avatar/devforum.zoom.us/rgoh/32/12091_2.png) [@rgoh](https://devforum.zoom.us/u/rgoh)\
**Post date:** [February 9, 2021, 6:57pm UTC](https://devforum.zoom.us/t/jwt-for-different-scopes/42381/2 "2021-02-09T18:57:00Z")

</div>

I am also interested in this functionality. I want to reduce scope since I don’t need admin level info all the time and would love to filter out the noise that is produced.

---

<div class="post-metadata">

**Author:** ![brijeshnp](https://avatars.discourse-cdn.com/v4/letter/b/cc9497/32.png) [@brijeshnp](https://devforum.zoom.us/u/brijeshnp)\
**Post date:** [November 11, 2021, 11:25am UTC](https://devforum.zoom.us/t/jwt-for-different-scopes/42381/3 "2021-11-11T11:25:39Z")

</div>

Here in link, zoom staff specified that

When using JWT, the API should know which user is trying to change the host and can make sure they have “schedule for” privilege

> [@](#):
>
> I have the same question (re using JWT to perform this action). This was working just fine until a few weeks ago. I already posted this question on another thread [here](https://devforum.zoom.us/t/api-error-patch-meeting-change-a-host-of-a-meeting-by-calling-api-with-an-error/11404/4). Thanks for any help on this one! Christian

But how to add username or admin account in jwt token so that we can change host of existing meetings using Rest API ?

Is there any way to specify that things, due to permission issue not able to change host of existing meetings