[URGENT] Any other alternative ways to handle Zoom's upcoming User Attribution Requirement?

Meeting SDK Web
1

Hi Zoom team,

We are evaluating options to comply with the upcoming User Attribution Requirement being enforced on February 23, and would appreciate clarification on what is supported vs. unsupported.

We understand the recommended approaches using ZAK or OBF tokens. However, our use case is not to create AI/Assistant apps but rather to support users without Zoom accounts to join external meetings. As a result, we are exploring whether there are ISV-based approaches that better fit our use cases.

Below are the options we are currently considering:
————————————————————————————————————
1. ISV-based approaches

Under an ISV partnership, we would like to understand whether the following models are supported:

a. Sub-accounts / internal meeting classification

  • Can external users who host meetings be onboarded as sub-accounts or customers under our main ISV account?

  • If so, would meetings hosted under these sub-accounts be considered “internal,” allowing SDK clients to join using JWT only (without ZAK or OBF)?

  • Would a single SDK app under the top-level ISV account be sufficient, or would each sub-account/customer require its own SDK app?

b. SDK app ownership / installation

  • Is it supported to programmatically create Marketplace SDK apps for external users and use their SDK keys to join meetings without OAuth?

  • If external hosts install our SDK app from the Marketplace, or are added as collaborators to our SDK app, would meetings hosted in their accounts be considered internal and allow SDK joins using JWT only?

  • Is this method only supported in ISV?

c. Managed users (custcreate)

  • If we create and manage users via the custcreate operation:

    • Can OAuth be performed programmatically on behalf of these users?

    • Can these managed users host or join meetings in external accounts while satisfying the attribution requirement?

d. ISV pricing

  • Can you share high-level ISV pricing guidance for the models above?

2. OBF token usage

  • Can a single internally controlled user obtain an OBF token that is reused across multiple SDK instances?

3. RTMS as an alternative

  • Does RTMS support gallery view?

  • Are there any public resources or high-level pricing guidance available for RTMS? We are looking at 5000 meeting hours per month at our peak usage across multiple customers.

Based on previous forum discussions, it appears there is currently no way to fully test or simulate behavior once the new requirement is enforced. Given this limitation, and the fact that we are actively engaging with Zoom Sales and the ISV team (with vendor procurement typically taking time), we would like to ask whether a temporary extension is possible to allow sufficient time to implement the correct solution.

Thank you for your guidance. Any clarification on supported vs. unsupported approaches would be greatly appreciated.

5 Likes
2

Curious about this as well, as our app is not for AI note taking and most of our users don’t have a Zoom account.

3

hi @StarKee ,

You say you want to:
”support users without Zoom accounts to join external meetings”

In what context are you doing this? If you provide a user with a link to the meeting you require them to join, can they join using the Zoom browser version?

As you do not explain anything about your app, I can not see what more to say.
Your suggestions are complicating the issue, so I assume this will be embedded in another app.
In any case, my approach would be

  1. Create a meeting
  2. Get meeting link
  3. Send the meeting link to the user or launch it on the screen. I would not use the Zak token because you are suggesting these people don’t have Zoom, and therefore don’t have a Zoom account.

You may want to pop in on our biweekly office hours. A short conversation would probably be easier than a conversation here. Also, if you paid to be an isv, then you would get a higher level of support than this forum.

all the best

John Drinkwater