App Marketplace
Looking for:
.
-
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. This includes performing actions such as scheduling and updating meetings, deleting meetings, and updating live streaming options. This scope allows an app to manage meeting information for a Master account's sub accounts. This scope allows an app to view a user's local recording meeting token information.
This scope allows an app to view an account's users' local recording meeting token information. This scope allows an app to view PAC details for all users in an account. This includes dedicated and global dial-in numbers, conference IDs, and passwords used to join a conference. This scope allows an app to view and manage the PAC information for all users in an account. This scope allows an app to view and manage PAC information for all sub accounts associated with a Master account.
The following are the available Phone scopes and associated API:. This scope allows an app to view details about a user's Zoom Phone. This includes phone numbers associated with the user, the user's Zoom Phone profile details and calling plans, site details, voicemails, and recordings of the user's phone calls. This scope allows an app to view Zoom Phone details for all users in an account. This includes phone numbers associated with users, users' Zoom Phone profiles and calling plans, site details, voicemails, and recordings of users' phone calls.
Back to scopes list or phone scopes. This scope allows an app with access to Zoom Phone management permissions and the app can perform actions such as updating users' Zoom Phone settings, Zoom Phone profile that includes information related to calling plans enabled for the user, email address of the user, and site details, adding and removing user phone numbers, managing auto-receptionist configurations, blocked lists, call queues, devices, common area phones, and phone sites.
The following are the available Cloud recording and Archiving scopes and their associated API calls:. This scope allows an app to view a user's meeting or webinar recordings. This scope allows an app to view all users' meeting or webinar recordings. This scope allows an app to view and manage a user's meeting or webinar recordings. This scope allows an app to view and manage all users' meeting or webinar recordings.
The following are the available Report scopes and their associated API calls:. This scope allows an app to view an account's meeting and webinar statistics via usage, user activity, meeting, and webinar reports.
This scope allows an app to view a Master account's sub accounts' meeting and webinar statistics via usage, user activity, meeting, and webinar reports.
The following are the available Role scopes and their associated API calls:. This scope allows an app to view an account's role details and assigned member information.
This scope allows an app to perform actions on behalf of an administrator. This includes creating a role, updating role details, and managing members' roles. This scope allows an app to view accounts' Zoom Room information, including Zoom Room profiles, settings, and locations.
This scope allows an app to perform actions on behalf of an administrator, including updating Zoom Room profiles, settings, and locations. This scope allows an app to provide support for provisioning users through the User resource for users that exist in a corporate account using identity providers.
This scope allows an app to manage SIP Phones configured on users' accounts. This scope allows an app to view and manage a Master account's sub accounts' SIP trunk configurations and numbers.
An app with this scope can perform actions such as adding internal call-out countries, adding new internal numbers, and deleting existing numbers. This scope allows an app to view tracking fields information for all users in an account. This scope allows an app to manage tracking fields. To release onto the Marketplace, all public apps must undergo a dedicated Submission Review process for information and functional review. Once an app has been submitted, the Marketplace team will conduct this review independently, but work directly with you on any additional requirements.
Once an app has been submitted, the Marketplace team performs a Security Audit and Penetration Test focused on maintaining security and resilience as well as protecting customer data. More details on security testing can be found in our Submission Review guide. All published apps are also required to provide individual on-going support for users.
While the Zoom Marketplace provides active support for the use of the platform, all apps are required to actively provide users with their own dedicated support options.
Make sure to note which Scopes your app would like to request, and any Event Subscriptions it would benefit from. If you're looking for help, try Developer Support or our Developer Forum. An example of an Account-level app could be an internal dashboard used by your company to create and manage meetings on behalf of your users. A User-managed app is an application which is installed by individual users, and thus requires authentication on behalf of each user.
User-managed apps allow an end-user to control the authorization and deauthorization of the app, allowing the user to protect and manage control of their Zoom account. JWTs are both compact and self-contained, allowing them to communicate all context and information about a user in a small JSON object, sent through a URL or simple request. JSON Web Tokens are used by Marketplace developers to authenticate access to their Account-level apps which allow an admin to manage their own account or users.
To allow applications to manage individual user data, the Zoom Marketplace provides direct support to OAuth2. OAuth apps are typically end-user applications which allow secure integration with Zoom APIs to access authorized data for each user.
OAuth apps can either be installed and managed across an account by account admins as an account-level app or by end-users individually as a user-managed app. Chatbots are account-level apps installed within the Zoom Client which interact with users using the chat interface. Developing a chatbot on the Zoom Client can easily be extended to meet a wide range of needs, allowing you as a developer to set custom commands, data connections, and chat-card formats.
Chatbots allow you to build full-featured apps that manipulate and respond within the Zoom Client chat. These apps can interact with all Zoom APIs, Webhooks, and third-party services, in the same way other app types might, and use the standard OAuth 2.
To learn how to build a chatbot that interacts with users on the Zoom Chat Client, reference our Build a Chatbot guide. Webhook-only apps use Event Subscriptions to integrate and connect third-party services to the Zoom platform when an action event is triggered.
Zoom app marketplace permissions.
- How to grant Shared Access Permissions during app authorization
Apps may be marketplave 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. Zoom app marketplace permissions 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 zoom app marketplace permissions receive an email with a link to an auto-generated App Перейти на страницу Report highlighting existing permissoins 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 zoom app marketplace permissions 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 zoom app marketplace permissions works, and permissione to get started. Include features, benefits, and any information which would help readers decide permssions your app provides value or solves their problem.
Zoom reserves the right to remove or require a revision привожу ссылку any content, in whole or part, including an app name, that ссылка these Requirements, the Marketplace Developer Agreement, the Zoom Terms of Service, our Community Standards, or for zoom app marketplace permissions other reason at our sole discretion. Highlight features or typical use cases of your app. Mmarketplace descriptions should be sentences a maximum of charactersand can be updated when submitting new versions.
Provide a Zoom app marketplace permissions 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 больше на странице does permisxions belong to you music, clips, etc. At least one image or video is required in preview по этому сообщению. Remember to use a high enough resolution to appear clearly on screens of varying sizes.
Select a category which zoom app marketplace permissions describes the main function and zoom app marketplace permissions of your app. Release Notes for the App Reviewer help the Marketplace narketplace effectively test your app. Be thorough as possible providing information on roles and permissions needed for effective functional testing.
App zoom app marketplace permissions without sufficient testing release notes may require resubmission. If you are upgrading an appyou 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 zoom app marketplace permissions 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, zoom app marketplace permissions emails, or unsubscribing to email permissioms. Contact Support Optional — Describe what users can expect when engaging your support team including the hours of your support team and zoominfo engage 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 Zoom app marketplace permissions 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 читать полностью to wait to hear from your support team.
Any domains receiving callbacks or requests ap 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 zoom app marketplace permissions ensure your zoom app marketplace permissions 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 zoom app marketplace permissions marketplacd 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 matketplace 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, zoom app marketplace permissions the following guidelines: Adding the App Required : A step by zoom app marketplace permissions guide for a user to add your app.
A simple list like the following will suffice, permssions 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 zoom app marketplace permissions 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 Permisions 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 zoom app marketplace permissions removal When an app has по этому адресу approved, the Marketplace team notifies you of approval and public availability of the app.
Need help?
Comments
Post a Comment