Webhook not triggering for co-host scenario in user-managed app

[gianni.zoom (Gianni)]

@zezulatomas

Concern:
I’m trying to understand why the webhook requires the meeting initator (User B in this scenario) to be registered with the app for successful triggering? This setup is especially problematic as the host often delegates meeting management to co-hosts after starting the session.

Could anyone shed some light on whether this is the expected behavior of webhooks involving co-hosts, or if there’s a potential oversight in webhook configuration for such scenarios? Any insights or recommendations for ensuring the webhook can trigger regardless of the host’s or co-host’s app association would be immensely helpful.

Thankful for any help or guidance.

Hi @zezulatomas , my initial assumption is that it has to with the privacy and user data management framework for published apps. Since the original creator of the meeting (User B) in the first example did not provide consent for the app to access their data, the webhook will not trigger.

Co-host =/= host and they do not assume full permissions available to original host so I am not surprised the app does not receive meeting event info if user b did not approve the app for their meetings.

I am moving this post to App Marketplace . @kwaku.nyante , can you offer some insight to confirm or clarify my response from the security perspective?