Set up a Zoom connector

C1 provides identity governance for Zoom. Integrate your Zoom instance with C1 to run user access reviews (UARs) and enable just-in-time access requests.

Availability

This connector works with Zoom on the Pro, Business, Business Plus, or Enterprise plan. The Zoom Basic plan is not supported.

Capabilities

Resource	Sync	Provision
Accounts
Groups
Roles
Licenses
Contact groups
Invites

Licenses are a derived resource type — Zoom exposes no /licenses endpoint, so license grants are emitted from the account sync using each user’s Zoom license tier. If licenses are excluded from the connector’s sync, accounts skip their grants pass entirely, since license grants are the only grants accounts emit.

Invites represent pending Zoom user invitations and are transient — they disappear once the invitee accepts. C1 syncs invites for visibility but skips sync anomaly detection on them, since their counts naturally fluctuate.

The Zoom connector supports automatic account provisioning.

The Zoom connector supports account deprovisioning (user deletion).

Connector actions

Connector actions are custom capabilities that extend C1 automations with app-specific operations. You can use connector actions in the Perform connector action automation step.

Action name	Additional fields	Description
transfer_and_delete_user	user_id (resource, required), action (string, required: disassociate or delete), transfer_email (string; requires at least one transfer option, and is required when one is set), transfer_meeting (bool), transfer_webinar (bool), transfer_recording (bool)	Reassigns a user’s meetings, webinars, and cloud recordings to another Zoom user, then removes the user from the account

To run this action, give the Zoom app the user:delete:user:admin scope. When you set transfer_email, C1 confirms that the recipient exists before removing the user, which requires user:read:user:admin — a scope the connector already needs to sync accounts. The transfer options do not require any additional scopes.

Gather Zoom credentials

Configuring the connector requires you to pass in credentials generated in Zoom. Gather these credentials before you move on.

A user with Account Owner status in Zoom must perform this task.

Create a Zoom OAuth app

1. Navigate to the Zoom App Marketplace.

2. Click Develop and select Build App.
3. Locate the Server-to-Server OAuth option and click Create.

4. Give your app a name, such as “C1” and click Create.
5. A page for the newly created app opens. Copy and save the Account ID, Client ID, and Client secret shown on this page.

Configure and activate the OAuth app

1. From the App Credentials page, click Continue.

2. On the Basic information page, fill out the form and click Continue.

3. On the Feature page, do not make any changes. Click Continue.

4. On the Scopes page, click + Add Scopes. Give the app the following set of scopes:

   • contact_group:read:list_groups:admin
   • contact_group:read:list_members:admin
   • group:read:list_groups:admin
   • group:read:list_members:admin
   • group:read:administrator:admin
   • role:read:list_roles:admin
   • role:read:list_members:admin
   • user:read:user:admin
   • user:read:list_users:admin
   • billing:read:plan_usage:admin (optional — required only if you want C1 to surface purchased vs. consumed Licensed seat counts)

   If you want to use C1 to provision and deprovision Zoom permissions, or to run the transfer_and_delete_user connector action, add these scopes as well:

   • role:write:member:admin
   • role:delete:member:admin
   • group:write:member:admin
   • group:delete:member:admin
   • user:write:user:admin (create users)
   • user:update:user:admin (required to assign/revoke a license tier)
   • user:delete:user:admin (delete users; also required for the transfer_and_delete_user connector action)
   • group:write:administrator:admin
   • group:delete:administrator:admin
5. Click Done. Review the list of scopes and click Continue.

6. On the Activation page, click Activate your app.

Done. Next, move on to the connector configuration instructions.

Configure the Zoom connector

To complete this task, you’ll need:

• The Connector Administrator or Super Administrator role in C1
• Access to the set of Zoom credentials generated by following the instructions above

Cloud-hosted

Follow these instructions to use a built-in, no-code connector hosted by C1.

1. In C1, navigate to Apps > Connectors and click Add connector.

2. Search for Zoom and click Add.

3. Choose where to add the connector: Create a new app, or Add to an existing app (then select the app).

   If you’re creating a new app, choose whether to link it to an application discovered from your identity provider: select Yes and pick the IdP application, or No to continue with just the connector.

4. Set the connector’s Name and, optionally, a Description.

5. Click the pencil icon next to Owners to choose who can configure and manage this connector.

6. Click Add. The connector is created and its configuration page opens.

7. Find the Settings area of the page and click Edit.

8. Enter the account ID for the new app into the Account ID fields.

9. Enter the Client ID and Client secret into the Client ID and Client secret fields.

10. Optionally, enable Sync Inactive Users to include deactivated Zoom users in the sync. When enabled, inactive users appear with a disabled status in C1. This is disabled by default.

11. Click Save.

12. The connector’s label changes to Syncing, followed by Connected. You can view the logs to ensure that information is syncing.

Done. Your Zoom connector is now pulling access data into C1.

Self-hosted

Follow these instructions to use the Zoom connector, hosted and run in your own environment.

When running in service mode on Kubernetes, a self-hosted connector maintains an ongoing connection with C1, automatically syncing and uploading data at regular intervals. This data is immediately available in the C1 UI for access reviews and access requests.

Resources

• GitHub repository: Access the source code, report issues, or contribute to the project.

Step 1: Set up a new Zoom connector

1. In C1, navigate to Apps > Connectors and click Add connector.

2. Search for Baton and click Add.

3. Choose where to add the connector: Create a new app, or Add to an existing app (then select the app).

   If you’re creating a new app, choose whether to link it to an application discovered from your identity provider: select Yes and pick the IdP application, or No to continue with just the connector.

4. Set the connector’s Name and, optionally, a Description.

5. Click the pencil icon next to Owners to choose who can configure and manage this connector.

6. Click Add. The connector is created and its configuration page opens.

7. In the Settings area of the page, click Edit.

8. Click Rotate to generate a new Client ID and Secret.

   Carefully copy and save these credentials. We’ll use them in Step 2.

Step 2: Create Kubernetes configuration files

Create two Kubernetes manifest files for your Zoom connector deployment:

Secrets configuration

# baton-zoom-secrets.yaml
apiVersion: v1
kind: Secret
metadata:
  name: baton-zoom-secrets
type: Opaque
stringData:
  # C1 credentials
  BATON_CLIENT_ID: <C1 client ID>
  BATON_CLIENT_SECRET: <C1 client secret>

  # Zoom credentials
  BATON_ACCOUNT_ID: <Zoom app account ID>
  BATON_ZOOM_CLIENT_ID: <Zoom client ID>
  BATON_ZOOM_CLIENT_SECRET: <Zoom client secret>

  # Optional: include if you want C1 to provision access using this connector
  BATON_PROVISIONING: true

  # Optional: sync deactivated Zoom users (disabled by default)
  BATON_SYNC_INACTIVE_USERS: true

See the connector’s README or run --help to see all available configuration flags and environment variables.

Deployment configuration

# baton-zoom.yaml
apiVersion: apps/v1
kind: Deployment
metadata:
  name: baton-zoom
  labels:
    app: baton-zoom
spec:
  selector:
    matchLabels:
      app: baton-zoom
  template:
    metadata:
      labels:
        app: baton-zoom
        baton: true
        baton-app: zoom
    spec:
      containers:
        - name: baton-zoom
          image: public.ecr.aws/conductorone/baton-zoom:latest
          imagePullPolicy: IfNotPresent
          env:
            - name: BATON_HOST_ID
              value: baton-zoom
          envFrom:
            - secretRef:
                name: baton-zoom-secrets

Step 3: Deploy the connector

1. Create a namespace in which to run C1 connectors (if desired), then apply the secret config and deployment config files.

2. Check that the connector data uploaded correctly. In C1, click Apps. On the Managed apps tab, locate and click the name of the application you added the Zoom connector to. Zoom data should be found on the Entitlements and Accounts tabs.

Done. Your Zoom connector is now pulling access data into C1.