Five Often-asked Questions About Zoom Marketplace App Submissions

Virginie
Wed, 12 Oct 2022 15:19:54 +0000
App Submission

QUESTION: During the app submission process, can a developer enable view permissions to internal users/developers to contribute to the development of the app? Can a developer enable edit permissions to internal users/developers to publish applications for distribution?

ANSWER: You can assign specific permissions (view or edit) to any internal developer who needs to be involved in the app development process.

Please note that before adding another user as a collaborator, you will need the required permission or you will get an error (as shown below). The user who wants to be added as a collaborator will need to have their permissions updated from the role/user setting.

Please Note: if a user was ever removed from the account, you will need to make sure you assign another user to take ownership of the App.
As a next step, you can add collaborators this way:

QUESTION: Is there a way to prevent specific end users from authorizing the application?

ANSWER: There is no active ‘user filter’ on the Marketplace, which means that developers cannot control who is able to search their app. Using the Landing Page install option, the developer can control which users can authorize their app by requiring user login on their landing page.

This will result in the public listing page showing ‘Visit Site to Add’ instead of instantly ‘Adding’ the app, users will be redirected to the 3rd party developer’s site to login to their 3rd party account before authorization:

Unlisted Apps:
If you don’t want your app to be visible on the Marketplace, we now have an option to unlist your app. Please check this page for additional information.

QUESTION: Can we use the same app for both our Production and Staging environments?

ANSWER: App submissions have a separate production and development client id and redirect URLs.

QUESTION: Once my app is published, can it be authorized by ANY user, or can we restrict access to my customers? Do my users have to authorize the app from the Zoom Marketplace?

ANSWER: The Zoom Marketplace is flexible enough to support any user onboarding or integration enablement process that your company uses. There are two ways for users to authorize your application and be redirected to your domain.

In order to support developers who want to provide Zoom functionality they have built to their own customers only (customers who have an account or pay for the developer’s product), Zoom Marketplace offers a ‘From your landing page’ authorization flow. This allows a developer to redirect users to their domain in the event that:

a. End Users need to have an account with the developer in order to access the developer’s Zoom integration

b. End Users need to be onboarded to the product before enabling the Zoom functionality

Once an End User is on the developer’s domain (for example: to login, onboard, paid Zoom feature, etc.), it is up to the developer to ensure a smooth and efficient user experience for adding the Zoom integration to their account.temp

If your company or application supports a ‘freemium’ or self-service model and you want users to discover and quickly add your app directly from the Zoom Marketplace, select ‘From Marketplace’ as the installation method in your Information section of the app build flow.

After authorization, users will be redirected to the URL you input in the ‘Redirect URL for OAuth’ field in the credentials section of the app build flow.

QUESTION: How do we handle any update we need to make to our application AFTER it was published on the Zoom App Marketplace ?

ANSWER: If you need to update your app AFTER it was published on our Marketplace, you will need to do it via an UDPATE request. These requests are easy to submit and don’t need as much time to be reviewed by a Zoom reviewer if the only changes are made to the meta data of your app.

If you need to request a change in scopes, please note that the process may be slightly longer, as Zoom reviewers will need to test each additional scope/removal of scope to make sure the functionality of your application still passes Functional review.

1 post - 1 participant