Skip to main content
All CollectionsIntegrationsVideocall
Zoom On-Premise installation
Zoom On-Premise installation

This article explains how Zoom can be used in an on-premises installation.

Alex avatar
Written by Alex
Updated over 7 months ago

In order for Zoom to be used in an on-premises installation, a Zoom client must be created and stored for this instance by the operator via the Zoom Marketplace.

The client must be created with the account that is used at anny.


Creation of a client

  1. Navigate to the Zoom App Marketplace and log in.

  2. Go to Develop > Build App.

  3. Click on Create in OAuth.

  4. Enter anny as the name of the app.

  5. Select Account-level app.

  6. The slider for "Would you like to publish this app on Zoom App Marketplace?" must be turned off.

  7. Create the app with Create.

  8. (Optional) Upload the anny logo for the app.

  9. Save the Client ID and the Client Secret and send them to us.

  10. Enter Redirect URL for OAuth https://app.$ownDomain/organization/integration/zoom/redirect and replace $eigeneDomain with the domain of the instance.

  11. Enter Add Whitelist URLs https://app.$ownDomain and replace $eigeneDomain with the domain of the instance.

  12. In the Information step, everything must be filled in according to the description. This is information that will not be public and can only be viewed by you.

  13. Enter the necessary scopes:

    1. Meeting > View all user meetings (meeting:read:admin)

    2. Meeting > View and manage all user meetings (meeting:write:admin)

    3. User > View all user information (user:read:admin)

  14. Enter the Client ID and the Client Secret at anny. Alternatively, contact us by e-mail.

What is a client?

This is an OAuth2 client. In abstract terms, an OAuth2 client is a third-party application that can perform actions on an application on behalf of a user with their consent. In this case, anny is a third-party provider and creates and obtains consent during the installation of the integration in order to create meetings for bookings.

Why do I need to create my own client?

A client is permanently bound to an instance. This provides a high level of security that only this instance can perform actions (create a meeting) with this client and the consent of users. Since a new instance of anny exists for an on-premises installation, a separate client must be created for this instance.

Did this answer your question?