# In-client Consent Screen

**URL:** <https://devforum.zoom.us/t/in-client-consent-screen/76502>\
**Category:** Zoom Apps\
**Created:** [September 26, 2022, 7:16am UTC](https://devforum.zoom.us/t/in-client-consent-screen/76502 "2022-09-26T07:16:28Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![jayesh](https://sea2.discourse-cdn.com/flex016/user_avatar/devforum.zoom.us/jayesh/32/39296_2.png) [@jayesh](https://devforum.zoom.us/u/jayesh)\
**Post date:** [September 26, 2022, 7:16am UTC](https://devforum.zoom.us/t/in-client-consent-screen/76502/1 "2022-09-26T07:16:28Z")

</div>

Hi,

I am doing authorization flow in my zoom app. So the problem is that when a user installs an app from an invitation or directly from the web, zoom asks users to authorize the app’s copes. That works fine but when we call the [authorize](https://marketplace.zoom.us/docs/zoom-apps/js-sdk/reference/#authorize) API of zoom SDK again after that it is asking for the same.

Our use-case:

When a user is logged in to the app and had already authorized the app’s scopes, we want to add non-interactive Oauth flow which should not be visible to the user. But whenever we invoke the [authorize](https://marketplace.zoom.us/docs/zoom-apps/js-sdk/reference/#authorize) API call of zoom SDK it redirects the user to the in-client consent screen.

Below I have attached the screen which I am getting after calling the ‘authorize’ API call.

 ![image](https://us1.discourse-cdn.com/flex016/uploads/zoomdeveloper/original/3X/f/7/f72c95725acdfbdf65d0c79044f7bdb803e5dedb.png)

---

<div class="post-metadata">

**Author:** ![MaxM](https://sea2.discourse-cdn.com/flex016/user_avatar/devforum.zoom.us/maxm/32/42303_2.png) [@MaxM](https://devforum.zoom.us/u/MaxM)\
**Post date:** [September 27, 2022, 7:40pm UTC](https://devforum.zoom.us/t/in-client-consent-screen/76502/2 "2022-09-27T19:40:56Z")

</div>

@jayesh As long as there weren’t any changes to the app between the web authorization and the in-client authorization you should be able to use the non-interactive flow.

As a first step, please make sure there weren’t any scope changes to the app and you’re authorizing within the client as the same Zoom User that you authorized on web.

If neither of those seem to be a factor, please reach back out and I’ll attempt to reproduce this behavior on my end.