Looking for:

Click here to ENTER


 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 

Apps may be submitted for Public release on the App Marketplace for all users to add. Once you have submitted an app, the Marketplace team conducts a Submission Review.

If approved, your app will be available on a public landing page featuring the app and through an embeddable button for all users to add. Fill out this form prior to submitting your app so that you can assess your app in its current state. Once you complete the assessment, you will receive an email with a link to an auto-generated App Review Report highlighting existing issues and recommendations on how to resolve those issues.

Creating a private app allows users on your account to add your app without releasing it publicly. It is highly recommended you test your app locally before submitting for approval. To authorize a local test, navigate to Local Test and click the Add button. Generate a Testable URL to share a locally developed app. Note: Locally developed apps can only be tested on the same account which developed the app. Your app listing is a public landing page for users on the App Marketplace. Use this section to tell users what your app does for them, how it works, and how to get started.

Include features, benefits, and any information which would help readers decide if your app provides value or solves their problem. Zoom reserves the right to remove or require a revision to any content, in whole or part, including an app name, that violates these Requirements, the Marketplace Developer Agreement, the Zoom Terms of Service, our Community Standards, or for any other reason at our sole discretion.

Highlight features or typical use cases of your app. Short descriptions should be sentences a maximum of characters , and can be updated when submitting new versions. Provide a Long Description which highlights the features of your app. Use this section to describe your App as a service, and your company as an organization. This is your opportunity to tell Zoom users why they should add this integration, what value does your app provide, and why your app is the right solution for them.

Ideal descriptions contain a concise, informative paragraph followed by a short list of main features. Long Descriptions can commonly cause an app submission to be denied if it lacks sufficient information about app functionality.

Long Descriptions can be updated when a new version of the app is submitted. A demo video in your app card is strongly recommended, but not required. Videos a maximum size of 40 MB should help users discover and learn about your app. Remember to not use content which does not belong to you music, clips, etc. At least one image or video is required in preview content. Remember to use a high enough resolution to appear clearly on screens of varying sizes.

Select a category which best describes the main function and purpose of your app. Release Notes for the App Reviewer help the Marketplace team effectively test your app. Be thorough as possible providing information on roles and permissions needed for effective functional testing. App submissions without sufficient testing release notes may require resubmission. If you are upgrading an app , you can provide Release Notes for the App Users. This information will be delivered directly to any app user who has opted to receive transactional emails from the Marketplace.

All published apps are required to provide a Documentation URL to guide users through adding and using the app. When creating documentation, provide the following guidelines:.

Adding the App Required : A step by step guide for a user to add your app. Link to a troubleshooting guide. Usage Required : For each feature or action, provide a clear use-case description and a list of any prerequisites. Removing the App Required : A guide to removing the app from your Zoom account. Notify the user the implications of deauthorization, and how you remove their data. Include any specific requirements by your app. A simple list like the following will suffice, as removing the app is handled by Zoom:.

Troubleshooting Optional, but highly recommended — List the most common user issues and their solutions including adding-app issues, adding meetings, accessing recordings, etc. FAQ Optional — List the most frequently asked questions, including questions on authorization, activation emails, or unsubscribing to email updates. Contact Support Optional — Describe what users can expect when engaging your support team including the hours of your support team and first response SLA maximum time a user should expect to wait to hear from your support team.

All published apps are also required to provide a Support URL for individual on-going support for users. While the Marketplace provides active support for use of the platform, all apps are required to provide users with their own dedicated support options. Describe what users can expect when engaging your support team including the hours of your support team and first response SLA maximum time a user should expect to wait to hear from your support team. Any domains receiving callbacks or requests from Zoom must be authorized.

Once this is completed, click Validate to allow the app to be submitted for review. Your submission must include a designated test account and credentials to support the Marketplace review team in functional and usability testing, in part to help ensure your app only has access to the APIs necessary for the app\’s functioning. If an account is not required to login to your app, select No account required.

When an app has been approved, the Marketplace team notifies you of approval and public availability of the app. From this point, any Zoom user is able to add your app using production credentials. For more information on this process, reference the Submission Review guide and the Submission Checklist. If the app has not yet been published, the app can be removed directly. If the app has been published, choose the change icon and select the option to Remove. Further status updates will be provided by email.

If you\’re looking for help, try Developer Support or our Developer Forum. Priority support is also available with Premier Developer Support plans. Want to ensure that your app is ready for submission? App Name and Branding Requirements When choosing a name, make sure that you: Create a distinct brand for your app. Content that indicates or implies Zoom endorses you or your app. Any content that attempts or appears to attempt to impersonate another person, account, or entity.

Generic terms or names that can be confused with an existing company or app. Long Description Provide a Long Description which highlights the features of your app.

Preview Content A demo video in your app card is strongly recommended, but not required. Categories Select a category which best describes the main function and purpose of your app. Documentation All published apps are required to provide a Documentation URL to guide users through adding and using the app. When creating documentation, provide the following guidelines: Adding the App Required : A step by step guide for a user to add your app. A simple list like the following will suffice, as removing the app is handled by Zoom: Login to your Zoom Account and navigate to the Zoom App Marketplace.

Support All published apps are also required to provide a Support URL for individual on-going support for users. Domain Validation Any domains receiving callbacks or requests from Zoom must be authorized. Test Account and Credentials Your submission must include a designated test account and credentials to support the Marketplace review team in functional and usability testing, in part to help ensure your app only has access to the APIs necessary for the app\’s functioning.

App approval and removal When an app has been approved, the Marketplace team notifies you of approval and public availability of the app. Need help?

 
 

 

 

The cookie is used to store the user consent for the cookies in the category \ »Analytics\ ». The cookie is used to store the user consent for the cookies in the category \ »Other.

The cookies is used to store the user consent for the cookies in the category \ »Necessary\ ». The cookie is used to store the user consent for the cookies in the category \ »Performance\ ». It does not store any personal data. Functional Functional. Functional cookies help to perform certain functionalities like sharing the content of the website on social media platforms, collect feedbacks, and other third-party features.

Performance Performance. Performance cookies are used to understand and analyze the key performance indexes of the website which helps in delivering a better user experience for the visitors. Analytics Analytics. Analytical cookies are used to understand how visitors interact with the website. These cookies help provide information on metrics the number of visitors, bounce rate, traffic source, etc.

These apps will not be displayed publicly on the App marketplace, and cannot be advertised in any public document or site. If your app requires additional time for beta testing, you can request to share your app outside of your account. This will be approved and monitored by the Marketplace team. When added and authorized, Marketplace apps are granted permission to make requests to the Zoom API on behalf of the user for the scopes they have requested.

Added apps do not have access to information for scopes they have not requested. Once the user authorizes, your app could make requests to the Meetings and Recordings APIs on their behalf; however, it would not have access to make requests to the Webinars API.

Reference the Permissions documentation for more information. User-added apps can be added on the Marketplace by any user. An example of a user-added app could be a scheduler which allows a user to create meetings on an outside platform. Admin-added apps can only be added by users who have account-level permissions.

This enables admins to control whether an app can be installed without pre-approval while in development using development credentials. Note: If pre-approval is required, users will not be able to install development apps for testing. As an admin, you also have access to enable or turn off email notifications about app pre-approval requests.

You can select up to five admins with Marketplace:Edit permission as recipients for the email notifications. Any of these admins can then accept or reject the pre-approval of the app. If you enable this option but do not add any recipients, the Zoom App Marketplace will automatically identify admins with the correct permissions and email them the notifications.

If an admin has pre-approved an app, it can be disabled by navigating to that app in the Marketplace and switching off the Pre-approve setting when needed.

Note: this will disable the app from all users in your account and should only be done if necessary. If a user is unable to install an app from the Marketplace, the user can view which missing permissions need to be granted before the app can be installed. Some apps may only be installed for users by account admins. These apps will show a Request to Install button available for users to send app installation requests to admins. Admins can view the app installation requests in the My Admin Dashboard and navigating to Request to Install.

Here admins can either install the app or reject the request. Clicking Uninstall will prompt a confirmation to remove the app.

 
 


 
 

Issue: Zoom updated app marketplace permissions as of November 30, , to allow users to authorize their shared access permissions.

This will allow you to use the app to take actions on your behalf for others you have access to, based on your permissions. In order for Class to invite users to the roster or add alternative hosts, any user that installed Class before November 30, , must go into the marketplace using the instructions below to enable shared access permissions for the Class for Users app. Contact Sales: Support English. Hit enter to search or ESC to close. Close Search. Platform: Class Version: All Issue: Zoom updated app marketplace permissions as of November 30, , to allow users to authorize their shared access permissions.

Search for:. We use cookies on our website to improve your experience. Manage consent. Close Privacy Overview This website uses cookies to improve your experience while you navigate through the website. Out of these, the cookies that are categorized as necessary are stored on your browser as they are essential for the working of basic functionalities of the website.

We also use third-party cookies that help us analyze and understand how you use this website. These cookies will be stored in your browser only with your consent. You also have the option to opt-out of these cookies. But opting out of some of these cookies may affect your browsing experience. Necessary Necessary. Necessary cookies are absolutely essential for the website to function properly. These cookies ensure basic functionalities and security features of the website, anonymously.

The cookie is used to store the user consent for the cookies in the category \ »Analytics\ ». The cookie is used to store the user consent for the cookies in the category \ »Other.

The cookies is used to store the user consent for the cookies in the category \ »Necessary\ ». The cookie is used to store the user consent for the cookies in the category \ »Performance\ ».

It does not store any personal data. Functional Functional. Functional cookies help to perform certain functionalities like sharing the content of the website on social media platforms, collect feedbacks, and other third-party features.

Performance Performance. Performance cookies are used to understand and analyze the key performance indexes of the website which helps in delivering a better user experience for the visitors. Analytics Analytics. Analytical cookies are used to understand how visitors interact with the website. These cookies help provide information on metrics the number of visitors, bounce rate, traffic source, etc. Advertisement Advertisement. Advertisement cookies are used to provide visitors with relevant ads and marketing campaigns.

These cookies track visitors across websites and collect information to provide customized ads. Others Others. Other uncategorized cookies are those that are being analyzed and have not been classified into a category as yet.

The cookie is set by GDPR cookie consent to record the user consent for the cookies in the category \ »Functional\ ». The cookie is set by the GDPR Cookie Consent plugin and is used to store whether or not user has consented to the use of cookies.

Laisser un commentaire

Votre adresse e-mail ne sera pas publiée.