When I schedule a new meeting and provide email addresses for my attendees, I expect them to get a robot-generated email invitation. They do not. And when I select "iCal" under "Calendar", I expect them to get a calendar invitation. They do not. Why? Might I have missed a critical preference setting or option?

How can I troubleshoot this?

I’m using the current latest Zoom version on MacOS Sonoma 14.1.1.

The blue start and stop is not working on trimming a recording. It is trimming the wrong portion or not doing it all. I do not see any videos on how to properly trim a recording. I just need to trim off the end of the recording and if I use the blue sliders it is only keeping that portion that I wanted to remove. Also AI support does not how to answer that question. 

Hi, I have scheduled a meeting VIA Microsoft Bookings with someone, but was never sent a link. I had a previous meeting through the same site this morning and when the time came, a link was never given and I ended up missing the meeting so I know that the link will not be provided upon meeting time. I have tried talking to your AI robot thing to help me with this problem but that just made everything worse and now I think I might be crazy. I did get a confirmation email about booking, but there is no link or directions. Please help me before I lose my ever-loving mind. How do I join my meeting tomorrow?

Hi there,

We have 7 users on our work account—1 owner and 6 members, all of whom are licensed. However, when scheduling meetings from the owner's account, I'm only able to schedule for 3 of the users instead of all 7.

Does anyone know how to resolve this so that I can schedule meetings for all users?

Thanks in advance!

We're facing an issue with our Zoom Marketplace app related to the OAuth flow. The app is approved and we have a redirect URI configured as beta.xyz.com. Recently, we set up a microservice to handle OAuth at a central location, and the new redirect URI is api.oauth.xyz.com/auth/zoom/callback.

We also manage different environments for our clients, so their respective redirect URIs would look like client.api.oauth.xyz.com/auth/zoom/callback. We added these to the allowlist in development mode, which automatically added them to the production allowlist, but the app is still not working for our customers.

I've read that if we add the root domain xyz.com, all subdomains should work for the OAuth redirect, especially since we're using Passport.js, which creates the redirect URI in  request body based on client environments. My question is, will this approach work without needing to add each client's redirect URI to the allowlist?