Recently I found that new users in my organization were no longer able to set up calendar and contacts integration with our Google Workspace account. Each time they clicked past the Google account selection screen, they got an alarming "This app is blocked" message.

I solved it by going to Admin > Account Management > Account Settings, scrolling to Calendar and Contacts, and deselecting the "Read" permission for Mail.

I hope this helps someone.

I am creating the app to integrate the recall ai bot but there is the required section called Links while creating the app in which there are several fields . My app will be in development mode and i don't have particulars url links to provide it , So what to add in those fields like Privacy Policy URL, Terms of Use URL,Support URL,Documentation URL,Direct Landing URL

Hi community, 

Could anyone share some insights on the following: 

We are going to create 'Zoom Events' in Zoom (not Zoom Webinars'). And we are planning to integration Zoom with Marketo. Which method is the 100% correct way to set this up? 

1) Using the Zoom for Marketo App from the Zoom Marketplace
https://support.zoom.com/hc/en/article?id=zm_kb&sysparm_article=KB0061861

Based on this documentation, it seems like the Native Zoom LaunchPoint service in Marketo ONLY works if you are creating Zoom webinars (not Zoom Events). Is this actually the case? 

Or 2) Add Zoom as a LaunchPoint service from Marketo side. (Does this Native integration only work with Zoom Webinars?)  
https://experienceleague.adobe.com/en/docs/marketo/using/product-docs/administration/additional-integrations/add-zoom-as-a-launchpoint-service

Thanks a lot!

We are getting this error on submitting app for security review - 

{
"code": -1,
"status": 400,
"error": "Bad Request",
"message": "Invalid URL: https://",
"timestamp": 1714061442011,
"trackingId": "MP_126d0c0f221a461a9bebaeb2b47d01c1"
}

I just bought a new PC laptop with Windows 11.   And it doesn't seem that the Zoom Plug-In for Outlook works for the latest version of Outlook.  I am so regretting moving from Windows 10 to Windows 11.   I relied heavily on the Zoom Plug-in to schedule my Zoom meetings.   Any work arounds for this issue?

 I'm writing to convey our desire to investigate the possibility of our companies working together. We are interested in integrating & publishing our cloud solution(redOrange.ai) with Zoom which I believe could provide significant value to both our customers and yours.

My app is currently undergoing a security review as part of the app review process. Some security vulnerabilities were identified and promptly addressed. Now, I need to resubmit the app for the marketplace team to reevaluate its security. However, upon attempting to publish, I encountered an error: "An error was encountered when processing your request." The network inspection revealed the following details:

{
"code": 500,
"status": 500,
"error": "Internal Server Error",
"message": "An error was encountered when processing your request",
"timestamp": 1713374865274,
"trackingId": "MP_df5b18432bf74f9e87c2f8eb5bc61a85"
}

Je suis administrateur de mon compte zoom et je suis en train de créer une nouvelle application OAuth de serveur à serveur, où je dois pouvoir préciser les portées « meeting:write:admin » et « user:write:admin ». Cependant, ces méthodes d'API ne sont plus disponibles ! Au lieu de cela, il semble qu'elles aient été renommées en « meeting:write:meeting:admin » et « user:write:user:admin ». J'ai précédemment créé des applications OAuth de serveur à serveur avec les méthodes d'API « meeting:write:admin » et « user:write:admin », et ces applications fonctionnent toujours actuellement. Comment puis-je créer une nouvelle application OAuth de serveur à serveur avec les méthodes d'API « meeting:write:admin » et « user:write:admin » ? Est-ce que je manque quelque chose de simple ? Merci d'avance pour tout retour ou solution à ce problème.

----------------------------

J'essaie de créer une nouvelle application OAuth de serveur à serveur, dans laquelle je dois pouvoir spécifier les étendues « meeting:write:admin » et « user:write:admin ».

Cependant, ces méthodes API ne sont plus disponibles !

Au lieu de cela, ils semblent avoir été renommés « meeting:write:meeting:admin » et « user:write:user:admin ».

J'ai déjà créé des applications OAuth de serveur à serveur avec les méthodes API « meeting:write:admin » et « user:write:admin », et ces applications fonctionnent toujours actuellement.

Comment puis-je créer une nouvelle application OAuth de serveur à serveur avec les méthodes API « meeting:write:admin » et « user:write:admin » ? Est-ce que j'ai raté quelque chose de simple ?

Merci d'avance pour tout retour ou solution à ce problème.