I’m adding the ability for the users of my web application to schedule and join Zoom meetings from within my web app and have everything working fine when I’m logged into the Zoom account used to create the OAuth App; however, whenever a different Zoom account is used, I get the following message:
When creating an OAuth App you are given the option to create one of two types of accounts: Account-level App or User-managed App.
Account-level = This app must be installed by admin and can manage all users in the account.
User-managed = This app can be installed and managed by individual users.
I choose the User-managed App as the option for my OAuth app as it sounds like that’s what I want. I want my users to be able to authenticate using their Zoom account.
What step or option am I missing or misunderstanding?
What do I need to do to allow my users to use their own Zoom accounts from within my web application?
Please let me know any additional information you may need to help me resolve this issue. I’d like to make this functionality available to my users ASAP, but won’t be able to until I get this issue resolved.
In order for users on different Zoom accounts to be able to use your app, it needs to first be published on our Marketplace and go through our submission process:
Without making your app publicly available, you will only be able to access it through users under your own Zoom account.
Okay. I will publish the app. Although, the terminology is a bit confusing. Because my Zoom app is not an independent app, but an integrated part of my existing web application, the concept of installing the Zoom app doesn’t seem to make sense to me. There is nothing for users to install.
