Approval workflow for enterprise users to request access to unconfigured apps

What’s changing 

We’re introducing a new approval workflow option for enterprise users to request access to third-party apps that have not been explicitly configured via App Access Control (AAC) by an admin. This only applies to apps which have not been configured. If a user is able to access an app today based on the policies configured by their admin, then there will be no change and they will continue to be able to access the app. 

When end users attempt to access unconfigured third-party apps and get blocked, they will see an error screen with an option to raise a review request to admins. After the user submits a request, admins will be able to review the end user requests in app access control and make a decision. 

This feature gives enterprise users a clear process for requesting access to apps they need, reducing the likelihood of them being completely blocked and improving their productivity. For admins, it provides a centralized and efficient way to manage and configure access for new applications within their organization, while maintaining control over data security. 

An example of the dialog that the end user will see when access is blocked, with an opportunity to request access 


The dialog an end user will see if they choose to request access 


The interface in the Admin console where admins can see and process access requests from users 


The interface admins can use to configure access by OU 


Who’s impacted 

Admins and end users 

Getting started 

  • Admins: 
    • This feature will be ON by default and can be enabled at the organizational unit (OU) level. You can enable the setting for users to request access to unconfigured apps in the Admin console under API Controls Settings. Visit the Help Center to learn more about user requests for unconfigured apps. 
  • End users: 
    • There is no end user setting for this feature. When the approval workflow is enforced, users will see a new screen that allows them to request access to the app from their admin. 

Rollout pace 


Availability

  • Available to all Google Workspace customers 

Resources 


Chrome Dev for Desktop Update

The Dev channel has been updated to 141.0.7354.3 for Windows, Mac and Linux.

A partial list of changes is available in the Git log. Interested in switching release channels? Find out how. If you find a new issue, please let us know by filing a bug. The community help forum is also a great place to reach out for help or learn about common issues.

Chrome Release Team
Google Chrome

Google Ads API documentation gets a major upgrade!

We're thrilled to announce significant improvements to the Google Ads API documentation, designed to make your development experience smoother, faster, and more intuitive. These changes are a direct result of valuable feedback from our incredible API developer community.

Our goal was simple: enhance discoverability and reduce the need to jump between pages, so you can spend less time searching and more time building. Let's dive into what's new:

1. Easier campaign type discovery and implementation

One of the most requested features was clearer guidance on supported campaign types. You can now more easily identify which campaign types the API supports and, crucially, find all the resources you need to implement them directly within the documentation. This streamlines your workflow from discovery to deployment.

2. Unified reporting and reference documentation

We've merged our Reporting and Reference documentation into a single location. This means all your essential references are now together, providing a more comprehensive and less fragmented experience when you're working with data and API specifics.

3. Seamless gRPC and REST integration

For those who switch between gRPC and REST, we've introduced a highly anticipated feature: a one-button toggle!

This lets you effortlessly switch between the two protocols on the same page. If you haven't yet, we highly recommend trying out our Try-it feature directly from the developer site. With gRPC and REST now co-located, accessing Try-it is more efficient than ever, making it perfect for quickly testing new features and requests.

4. Reorganized and clustered guides

All your familiar guides are still there, but we've given them a thoughtful re-ordering. Guides with similar features are now clustered together, creating a more logical flow and helping you navigate to related topics more quickly. This thoughtful reorganization aims to reduce friction and enhance your learning.

We want your feedback!

These changes are just the beginning, and your feedback is crucial as we continue to refine and improve. If you have any thoughts on these updates, or suggestions for future enhancements, please click the Send Feedback button at the bottom of any page in the documentation.

This direct line lets you provide valuable input that will help shape the future of the Google Ads API documentation.

We're incredibly excited about these updates and believe they will significantly enhance your experience with the Google Ads API. Happy coding!


Accelerating development with monthly releases for Android Studio – releasing 2X more often than before

Posted by Xavier Ducrohet – Tech Lead, Android Studio and Adarsh Fernando – Group Product Manager, Android Studio

Last year, we doubled our release frequency for Android Studio with the introduction of Feature Drops, a change designed to bring you new features and improvements more quickly. Today, we're excited to announce the next evolution in our release schedule: we're moving to monthly stable releases of Android Studio.

This new cadence means you’ll be able to get your hands on the latest features and critical improvements, faster than ever before. Here's what you can expect: every few months, we’ll introduce a version that contains the latest IntelliJ platform version, such as Android Studio Narwhal based on IntelliJ 2025.1. You’ll then see Feature Drops each month that include important bug fixes and new functionality you’ll want to try out, until it’s time to release Android Studio with the next platform version of IntelliJ.

Android Studio Narwhal release cadence 2025

You’ve actually already experienced this new release cadence with Android Studio Narwhal! In the last Feature Drop release we were able to take features such as Agent Mode from Canary to the Stable channel faster than ever before, making it possible for you to try out new features, faster!

Why Monthly Releases?

You told us waiting for the next major release to get a critical bug fix or a quality-of-life improvement can be frustrating. With the move to monthly releases, we can deliver these updates to you without the long delays. This means you'll have access to the features you want and the fixes you need, right when you need them. It's important to note that the Android Emulator and the Android Gradle Plugin will continue to be updated separately from Android Studio at a pace of every two months. And, as always, you don't need to update these components to download and use the latest stable version of the IDE each month.

Our Commitment to Quality

A faster release cadence doesn't mean a compromise on quality. In fact, our ability to release more frequently is a direct result of our long-term investment in our testing infrastructure. This effort began with Project Marble, a concerted effort to improve the quality and testing of Android Studio. Since then, we've been continuously improving and tooling our testing strategy to be more reliable, and to get feedback from those tests faster. Last year, we reached a point where we could confidently double our releases, and now, we're ready to take the next step with monthly updates. This means you’ll see releases 2X more often than before!

We're also continuing to provide early access to stable-ready releases. Previously, we’ve provided these opportunities first through Beta releases. With our investments in detecting and addressing issues earlier, we’re able to take a release from Canary directly into our Release Candidate (RC) channel with a stable-ready level of quality and polish. This gives you a chance to try out the latest features and improvements before they're released to the stable channel and to provide us with valuable feedback.

Update Monthly and Help Us Improve

We encourage you to update to the latest stable version of Android Studio each month to take advantage of the latest features and improvements. Your feedback is essential to helping us make Android Studio the best it can be.

Here's how you can get involved:

    • Download Android Studio Narwhal 3 Feature Drop: It’s currently available in the Canary channel and is the best way to get early access to new features and to provide us with feedback before a release is finalized. If you want a more stable build, download this version as soon as the Release Candidate becomes available.
    • Report a bug: If you encounter an issue, please let us know by reporting a bug. This helps us to identify and fix issues more quickly.

We're excited about this new chapter for Android Studio and we're confident that it will help you to build better apps, faster. As always, you can be part of our vibrant Android developer community on LinkedIn, Medium, YouTube, or X.

Test on a fleet of physical devices with Android Device Streaming, now with Android Partner Device Labs

Posted by Adarsh Fernando – Group Product Manager, Android Studio, and Grant Yang – Sr. Product Manager, Omnilab

Today, we're excited to give you an update on Android Device Streaming and announce that Android Partner Device Labs are now stable and available in the latest stable release of Android Studio Narwhal Feature Drop!

moving image of Android Device Streaming functionality in Android Studio Narwhal Feature Drop

Streamline your testing with Android Device Streaming

Android Device Streaming, powered by Firebase, allows you to securely connect to remote physical Android devices hosted in Google's secure data centers. This means you can test your app on a wide variety of devices and Android versions without leaving Android Studio, or having to purchase every device you want to test. This helps you:

    • Test on the latest hardware: Get your hands on the newest devices, including those not yet available to the public.
    • Cover a wide range of devices: Test on various form factors, from phones to foldables, from a multitude of manufacturers.
    • Improve developer productivity: Save time and resources by testing on real devices directly from your development environment.

At Google I/O 2025 earlier this year, we announced that Android Device Streaming graduated to stable. With that, we added the latest Google Pixel devices to the catalog, including the Pixel 9, Pixel 9 Pro, Pixel 9 Pro XL, and Pixel 9 Pro Fold. We are also working to add the upcoming Pixel 10 devices to the catalog soon.

We also announced that we are partnering with leading OEMs to bring you an even greater selection of devices through Android Partner Device Labs. And best of all, with our monthly quota of minutes, you can start testing Android Device Streaming with a wide range of devices at no cost. Usage beyond the monthly quota of minutes may incur a charge, as described on the Firebase pricing page.

Introducing Android Partner Device Labs

Android Partner Device Labs are now stable and available in Android Studio Narwhal Feature Drop. Android Partner Device Labs give you access to a fleet of physical devices from our OEM partners, including Samsung, Xiaomi, OPPO, OnePlus, vivo, and more. This gives you the ability to test your apps on the specific devices your users have, ensuring a better user experience for everyone.

Here are some of the devices available today through our partners:

Android Partner Device Labs featuring a fleet of physical devices from our OEM partners, including OPPO, OnePlus, Samsung, Xiaomi, and vivo, in Android Studio Narwhal Feature Drop

Get started with partner devices

To start using devices from Android Partner Device Labs, follow these steps in Android Studio:

  1. Open the Device Manager by navigating to View > Tool Windows > Device Manager.
  2. Click on the Firebase icon and log in to your Google Developer account.
  3. Select a Firebase project with billing enabled.
  4. You will now see the list of available devices, including those from our partners.

For team development, a Firebase project administrator (Owner or Editor) will need to enable access to each OEM's lab of devices. To do so, the admin should go to the Google Cloud project page, ensure the correct project is selected, and then enable the desired device lab by using the toggle and following the on-screen prompts. Once enabled, the entire team will have access to those devices in Android Studio.

Android Device Streaming Pricing

You can learn more about Android Device Streaming quota and pricing on the Firebase pricing page. Devices in the Android Partner Device Labs are available at the same pricing and with the same monthly quota of minutes at no cost as all other devices in the Android Device Streaming catalog (unless otherwise specified).

Wrapping it up

Android Device Streaming, now with the addition of Android Partner Device Labs, gives you an unparalleled selection of physical devices to test your apps. With a growing catalog of devices from Google and our OEM device partners, you can ensure your app works flawlessly for all your users.

We invite you to download the latest stable release of Android Studio and try out Android Device Streaming and the new Android Partner Device Labs. With our generous monthly quota, you can start testing on a wide range of devices at no cost. We are constantly updating the device catalog, so be sure to check back often for new additions.

Happy streaming!

Chrome Dev for Desktop Update

The Dev channel has been updated to 141.0.7354.2 for Windows, Mac and Linux.

A partial list of changes is available in the Git log. Interested in switching release channels? Find out how. If you find a new issue, please let us know by filing a bug. The community help forum is also a great place to reach out for help or learn about common issues.

Chrome Release Team
Google Chrome