Background

The Worklytics platform collects and analyzes workplace data at the instruction of Customer Organizations on their behalf, in accordance with our Privacy Policy, Terms of Service, and any customer agreement / laws / regulations which may supersede those terms. The Customer Organization remains the controller of this data and may instruct Worklytics to halt processing and destroy it at any time.

“Data Connectors” conceptualize the collection of workplace data, representing the connection via which Worklytics will collect data from a single data source.

Zoom is a video conferencing solution.

Worklytics Data Connector is a Zoom application

How Worklytics Uses Zoom Data

• User email address / personal info - Worklytics uses the email address and personal info (e.g. name, identity information) of your Zoom account and those users within your Zoom organization to match Zoom identities to other workplace applications.

• Zoom accounts - Worklytics processes basic accounts data to provide workplace and people analytics services. This data is used to match personsʼ identities in Zoom with other data sources and to provide groupings of persons for analytics proposes.

• Meetings data - Worklytics analyzes past meetings data, such as meeting start and end times, duration, number of participants and their basic info (display name, email, and Zoom id if present), to understand collaboration between people inside your organization and provide analytics services.

• Dashboard meetings data - Worklytics will use dashboard metrics (when the account has the feature available) to read information of past meetings more efficiently and to read quality of service information of past meetings (whenever present).

• Cloud recording meetings data - If your organization saves cloud recordings, Worklytics can analyze some of their data (chat, transcript and timeline, if available) and provide greater detail on collaborations. No content is stored on our platform, it will only be analyzed to improve the details of collaboration between people.

You can read details on the permission grant scopes at the end of this document.

Install Instructions

Follow these steps to connect your Zoom data to an existing Worklytics account.

1. Navigate to Zoom Marketplace (https://marketplace.zoom.us/) and search for "Worklytics". Select the Worklytics Analytics Connector application. Alternatively, inside Worklytics dashboard you can navigate to Data Connections > Zoom (if so, skip to step 3).

2. Click on "Install". It will redirect you to Worklytics' website, to the Zoom integration landing page.

3. Click on the Connect button.

4. You will need authenticate with your Zoom credentials and grant permissions for Worklytics to fetch data.

5. When finished, the authentication browser window/tab will close.

Usage

Upon installing the Worklytics Connector, an initial data fetch will trigger. Depending on your company size it might take some time to fetch, process and analyze all data.

Afterwards, Worklytics fetches new data on a daily basis.

Once data is analyzed and processed, customers can browse different trends derived from their Zoom usage in the "Explore Trends" section.

Uninstallation

There are two ways to uninstall the Worklytics Analytics Connector.

Uninstalling from Worklytics.co

Simply browse to your Data Connections, Zoom section, choose which one to uninstall and click on the Remove link.

Uninstalling from Zoom Marketplace

From Zoom's marketplace, you can navigate to Manage -> Installed Apps and from there click on the Uninstall button to remove it.

FAQ

Q: Why Recent meetings not taken into account for collaboration metrics?

A: Worklytics fetches new data once per day, so if you just had your meeting, it might take a few hours until the event gets processed.

How Worklytics Collects and Uses Zoom Data

Worklytics supports connecting to Zoom to analyze how people are collaborating via past meetings.

To support this, Worklytics Zoom connector request the following scopes: For apps prior to Apr 2024, classic scopes (valid up until 2025). Eventually will be migrated to granular scopes (See below).

• dashboard_meetings:read:admin Read information of past meetings, read quality of service information of past meetings.

• meeting:read:admin Read information from each meeting: metadata, occurrences, participants, ...

• recording:read:admin Read information about past meeting cloud recording data (if present): Chat, transcript, timeline.

• report:read:admin Read participants information about past meetings.

• user:read:admin Read Zoom users data, which includes the PMI personal meeting identifier (when enabled) and all email addresses per user, to better match users across data sources.

For apps created on or after Apr 2024, new granular scopes:

• user:read:list_users:admin, read users data, which includes the PMI personal meeting identifier (when enabled) and all email addresses per user, to better match users across data sources.

• meeting:read:list_past_participants:admin, read participants information about past meetings.

• meeting:read:list_meetings:admin, list meetings

• meeting:read:meeting:admin, read information from each meeting: metadata, occurrences, participants, ...

• report:read:user:admin, get meeting reports for a user.

• report:read:list_meeting_participants:admin, list participants of a meeting using reports API

Further reading: Zoom OAuth Scopes

Worklytics Service Level Agreement (SLA)

You can read about the Worklytics SaaS Platform Service Level Agreement (“SLA”) here: https://www.worklytics.co/worklytics-services-level-agreement-sla/

The following table(s) contains detailed examples of the metadata fields available from the Zoom API endpoints Worklytics leverages. In order to pseudonymize and sanitize PII and other potentially sensitive data, Worklytics provides access to a , which allows customers to pre-filter metadata, within customer infrastructure, before it is sent to Worklytics for processing.

These are the fields Worklytics recommends but the Worklytics DLP Proxy provides full field-level control and therefore any field may be removed or sanitized.

Field descriptions are taken from third party API documentation, these are maintained on a best effort basis and Worklytics can not guarantee their indefinite accuracy. Please refer to the source API site for the most up-to-date documentation.

Worklytics requires access to the following API primary endpoints:

MeetingParticipant

Meeting

User