KeySkopeAvailable · Reviewed 2026-09-18
Before you start
- A Zoom account with permission to create an account-level app.
- An administrator authorised to approve its read scopes.
Read-only permissions
| Setting | Purpose / value |
|---|---|
| user:read:list_users:admin | Read account users. |
| role:read:list_roles:admin | Read roles. |
| role:read:list_members:admin | Read role membership. |
Connect Zoom
- In Zoom App Marketplace → Develop → Build App, create a Server-to-Server OAuth app where your account supports it.
- Record its Account ID, Client ID and Client Secret. Add only the three read scopes listed here.
- Complete the app’s required information and activate it.
- Enter all three values in KeySkope and run the first sync.
- If using the existing General App OAuth flow instead, use an admin-managed app and the exact redirect URL supplied by your KeySkope deployment; leave Account ID blank. Authorise the app when redirected.
- Compare an active and inactive account, licence type and role membership with Zoom.
Connection fields
| Setting | Purpose / value |
|---|---|
| account_id | Required for Server-to-Server OAuth; blank only for the General App flow. |
| client_id / client_secret | OAuth application credentials. |
What appears in KeySkope
- User account status, available last sign-in, licence type and account roles.
- No meeting content, recordings or chat. A missing login timestamp stays unavailable.
Verify the first sync
- Wait for the sync to finish and review its status and any partial-collection notes.
- Compare the same account population in both systems. Check an account identifier, status and assigned role—not just the total.
- For a controlled test account, change its access in the source, sync again and verify the result. Keep approvals in your normal process.
- Record the credential owner and expiry. Rotate the credential in the source, update KeySkope and verify another sync before retiring the old credential.
Troubleshooting
| Setting | Purpose / value |
|---|---|
| Scope error | Match the granular scopes to users, roles and role-members endpoints; reauthorise if using General App OAuth. |
| Authentication failed | Do not mix General App credentials with a Server-to-Server Account ID. |
Official references
Vendor documentation reviewed on 2026-09-18. Setup has been checked against the connector implementation. A documentation review is not a live validation of every plan or tenant.
Ready to connect?
Open Connectors in your KeySkope workspace. Enter credentials only in the authenticated connection form.
Use your organisation’s dedicated KeySkope URL from an allowed network. Your workspace administrator can provide the address.