Create a new API endpoint that would allow us to enable selected user settings for all organization users at once

We’d like to request a feature for a new API endpoint that would allow us to enable selected user settings for all organization users at once. We’d basically want this request:

developers(.)zoom(.)us/docs/api/rest/reference/user/methods/#operation/userSettingsUpdate

that works in bulk, for all the users in the Zoom instance.

Right now after matching the users with the Zoom users we send a single request per user, and if we don’t want to violate the Zoom API rate limits, it takes a long time for our big account customers.

Ideally, the endpoint would respond with HTTP 200 and an array of objects with all the organizations users settings.

Thanks!

hi @WiktorPlaga

This is a good and valid request, but can I challenge you to whether much of this is available by select the users in the user groups feaure. And which settings you are interested in and why.

Zoom likes to limit usage for security reasons, so what features are you interested in?

All the best

John

2 Likes

Hey @expertswho, thanks for your reply!

Zoom users groups approach would make sense if we needed the settings only for our own organization, but the case is we need them for our users, who have their own Zoom organizations.

Asking them to setup “Zoom user groups” to use our app with Zoom would require a lot of work on their part, would be prone to errors (such as forgetting about some users), and at last wouldn’t be very user friendly (it wouldn’t “just work”) - we’d rather stick to the current approach of sending a single request per user instead.

I don’t see the usage limitation applying any security measures in this particular scenario, because we do adjust all the settings already - it just takes a lot of time (~0.67s per user, so our - and your - customer with 5k+ users needs to wait for almost an hour) due to requests throttling implemented on our part, so we don’t exceed the Zoom API limit.

Here’s the list of Zoom user settings we need turned on for organizations that integrate with our product, and why:

{
  recording: {
    // Controls whether the recordings are captured on cloud vs on premise (we require them to be on cloud for them to be accesible)
    cloud_recording: true
    // Setting related to timelines/transcript availability
    record_speaker_view: true
    // Setting related to timelines/transcript metadata
    show_timestamp: true
    // Setting related to timelines/transcript availability
    recording_audio_transcript: true
  }
  in_meeting: {
    // Feature that allows our multi-language transcript to work
    language_interpretation: { enable: true }   }
}

hi @WiktorPlaga ,
Your approach will work fine.
However, I speak with many corporations, and there are always concerns about privacy and security.
As an administrator, I could be concerned that your app is proliferating across my organisation, and you are gaining the ability to access all recordings.

Some of these transcript-capturing apps used this method and became a nuisance to the point that some organisations started banning them.

I am not an employee of Zoom or a representative of. My view is personal and based upon my experience and conversations.

Good luck with the app

John

OK @expertswho, thanks for your input!

We decided to request this feature of Zoom API solely based on our users feedback - our customers orgs did struggle with having all their employees setup our app to work with Zoom, and when we added the ability for admins to integrate it by themselves, they rightfully complained about the performance.

Other than that we did nothing new in terms of users settings, we requested exactly the same settings as we did before.

Our perspective based on conversations with the enterprise customers is that they don’t want to miss out on our features due to their employees misconfiguring their setup, so exactly the opposite!

No privacy nor security concerns were raised whatsoever.