We’re introducing new tools and resources for nonprofits to learn more about Google AI tools.
3 new ways nonprofits can put AI to work
We’re introducing new tools and resources for nonprofits to learn more about Google AI tools.
We’re introducing new tools and resources for nonprofits to learn more about Google AI tools.
These AI features can help you craft a menu, design a tablescape, and handle other party-planning tasks.
Google Search data reveals a growing desire to unplug and connect in real life with local run clubs, mahjong lessons and more.
It might sound counterintuitive, but Search's AI tools can actually help you make the most of your time offline whether you want to book concert tickets or find the perf…
We’re launching the AI Startup Support Program to accelerate innovative AI-native Japanese startups.
Google Cloud is now providing high-performance computing infrastructure for NOAA’s supercomputing system.
As part of improving security for Google Ads accounts, the Google Ads API will start requiring passkeys for Google Ads API users. This is part of a broader change in Google Ads that requires passkeys to authorize sensitive actions in your Google Ads account. These important security updates will start rolling out from August 5, 2026, and will be enabled for all users over the next few weeks.
Once this change goes live, users following the user authentication workflow to generate new OAuth 2.0 refresh tokens for Google Ads API will always be required to authenticate using a passkey. If you haven't created a passkey, you will be asked to create one, and use it to complete the authentication workflow. Other forms of authentication that use password alone, or 2-factor authentication (2FA) mechanisms such as Time-based One-Time Password (TOTP) or SMS-based codes will be disallowed.
You may be affected by this change, depending on the authentication workflow that your application uses.
To set up a passkey,
Google products that use Google Ads API, such as Google Ads Editor, Google Ads scripts, BigQuery Data Transfer Service or Data Studio to manage Google Ads will also start requiring a passkey-based authentication. If you don’t have passkeys enabled, you will be prompted to add one.
To learn more about how to set up passkeys, visit the Help Center. If you encounter issues, you can contact support.
For any questions or further discussion regarding this update, please connect with us on the "Google Advertising and Measurement Community" Discord server.
In the coming weeks, we’re starting the rollout of visual screenshots for the ‘Take notes for me’ feature in Google Meet. Visual screenshots automatically capture presented content (such as slides, diagrams, and charts) directly into the generated meeting notes document, ensuring critical visual context is preserved alongside spoken summaries and transcripts.
Ahead of the general availability rollout, admins can decide whether visual screenshots of presented content are allowed in meeting notes for their users and pre-configure their preferred setting in advance. Admin controls can be configured to either always allow screenshots of presented content (default) or only allow them when a meeting recording is enabled.
We’ll share another update on the Workspace Updates blog with more details when visual screenshots begin rolling out to end users.
While meeting transcripts accurately capture what is said during a call, they don’t currently include visual context—such as presented slides, financial charts, or architecture diagrams. Visual screenshots will soon be automatically embedded into the Google Doc created by “Take notes for me”.
In the coming weeks, we’re starting the rollout of visual screenshots for the ‘Take notes for me’ feature in Google Meet. Visual screenshots automatically capture presented content (such as slides, diagrams, and charts) directly into the generated meeting notes document, ensuring critical visual context is preserved alongside spoken summaries and transcripts.
Ahead of the general availability rollout, admins can decide whether visual screenshots of presented content are allowed in meeting notes for their users and pre-configure their preferred setting in advance. Admin controls can be configured to either always allow screenshots of presented content (default) or only allow them when a meeting recording is enabled.
We’ll share another update on the Workspace Updates blog with more details when visual screenshots begin rolling out to end users.
While meeting transcripts accurately capture what is said during a call, they don’t currently include visual context—such as presented slides, financial charts, or architecture diagrams. Visual screenshots will soon be automatically embedded into the Google Doc created by “Take notes for me”.
In the coming weeks, we’re starting the rollout of visual screenshots for the ‘Take notes for me’ feature in Google Meet. Visual screenshots automatically capture presented content (such as slides, diagrams, and charts) directly into the generated meeting notes document, ensuring critical visual context is preserved alongside spoken summaries and transcripts.
Ahead of the general availability rollout, admins can decide whether visual screenshots of presented content are allowed in meeting notes for their users and pre-configure their preferred setting in advance. Admin controls can be configured to either always allow screenshots of presented content (default) or only allow them when a meeting recording is enabled.
We’ll share another update on the Workspace Updates blog with more details when visual screenshots begin rolling out to end users.
While meeting transcripts accurately capture what is said during a call, they don’t currently include visual context—such as presented slides, financial charts, or architecture diagrams. Visual screenshots will soon be automatically embedded into the Google Doc created by “Take notes for me”.