# OAuth app scopes update email

**URL:** <https://devforum.zoom.us/t/oauth-app-scopes-update-email/76907>\
**Category:** App Marketplace\
**Tags:** oauth\
**Created:** [October 4, 2022, 9:46am UTC](https://devforum.zoom.us/t/oauth-app-scopes-update-email/76907 "2022-10-04T09:46:21Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![chrisf](https://sea2.discourse-cdn.com/flex016/user_avatar/devforum.zoom.us/chrisf/32/33092_2.png) [@chrisf](https://devforum.zoom.us/u/chrisf)\
**Post date:** [October 4, 2022, 9:46am UTC](https://devforum.zoom.us/t/oauth-app-scopes-update-email/76907/1 "2022-10-04T09:46:21Z")

</div>

Hi there,

We are about to update our OAuth app so that it includes new scopes to support the new features we will release on our platform soon. I have a few questions regarding the user re-authorization process that is triggered through the email they will receive.

1. I understand there is no option to not send this email to users. Is this correct?
2. Does re-authorization invalidate existing access and refresh tokens?
3. Is there a webhook we can use to be notified of re-authorizations?

---

<div class="post-metadata">

**Author:** ![ojus.zoom](https://sea2.discourse-cdn.com/flex016/user_avatar/devforum.zoom.us/ojus.zoom/32/734_2.png) [@ojus.zoom](https://devforum.zoom.us/u/ojus.zoom)\
**Post date:** [October 4, 2022, 6:44pm UTC](https://devforum.zoom.us/t/oauth-app-scopes-update-email/76907/3 "2022-10-04T18:44:43Z")

</div>

Hi @chrisf

1. We notify all subscribers when an app they have added gets an UPDATE request approved which contains scope changes. This notification includes the release notes for users that the dev provides as well as our UPDATE transactional email template. We cannot disable it.

2. Yes reauthorization will invalidate exisiting tokens.

3. Check this one: [Zoom API Events - App](https://marketplace.zoom.us/docs/api-reference/app/events/#operation/app.authorization_request_created)

---

<div class="post-metadata">

**Author:** ![kshrivastava](https://sea2.discourse-cdn.com/flex016/user_avatar/devforum.zoom.us/kshrivastava/32/39796_2.png) [@kshrivastava](https://devforum.zoom.us/u/kshrivastava)\
**Post date:** [October 21, 2022, 10:26pm UTC](https://devforum.zoom.us/t/oauth-app-scopes-update-email/76907/4 "2022-10-21T22:26:52Z")

</div>

@ojus.zoom Thanks for the response Ojus! Could you share an example of how this transactional email template looks like? Is it recommended to include a reauth link or instructions for the users in the dev release notes? Or are they already part of the template and will be redundant?

---

<div class="post-metadata">

**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:** [November 3, 2022, 7:46pm UTC](https://devforum.zoom.us/t/oauth-app-scopes-update-email/76907/5 "2022-11-03T19:46:54Z")

</div>

This topic was automatically closed after 30 days. New replies are no longer allowed.