Skip to main content
keni
keni
Level 2.0: Eclair
August 26, 2026
Question

Feature Request: Disable Chrome Address/Search Bar on Android Enterprise Fully Managed Devices

  • August 26, 2026
  • 3 replies
  • 125 views

We use Google Chrome on Android Enterprise Fully Managed shared devices. Chrome is required for several business use cases including Chrome Custom Tabs (CCT) authentication flows and PWA/web applications.

Our environment follows a shared-device model where associates check devices in and out throughout the day. While Chrome is needed for business workflows, users can sometimes reach the full Chrome browser through links opened from applications, authentication flows, PWAs, or other navigation paths.

Unless I'm missing something, I have not found a supported Chrome Enterprise app configuration that allows administrators to disable or hide the Chrome address/search bar (omnibox) on Android managed devices. Current options appear to be URL allowlists and blocklists. 

The challenge with URL-based controls is that they can become difficult to maintain at scale. Business applications often introduce new URLs, redirects, and endpoints over time, which can create ongoing administrative overhead and potential access issues.

A feature request we would love to see is a managed configuration that disables or hides the omnibox while still allowing Chrome to be used for approved business purposes such as CCT authentication and managed web applications. This would help prevent users from freely browsing non-work websites if they reach the browser while still preserving required business functionality.

Microsoft Edge currently offers similar controls, but we would prefer to continue using Chrome as our enterprise browser.

Is there another recommended approach today for Android Enterprise Fully Managed shared devices that allows Chrome to support CCT/PWA use cases while preventing general web browsing without relying on large URL allowlists and blocklists?

Thanks!

3 replies

Moombas
Moombas
Level 4.4: KitKat
August 27, 2026

Did you try web-app from your (possible used) managed google play account?

There you can choose fullscreen mode (neven no status or navigation bar but nor URL bar, maybe too much) or Independent (i hope translation is correct; with navigation and status bar but still without URL bar).

keni
keniAuthor
Level 2.0: Eclair
August 27, 2026
 

Thanks for the suggestion. We do use PWAs, and standalone/fullscreen mode works well for those scenarios. Our challenge is with native third-party Android applications that open Chrome Custom Tabs (CCT) for authentication or provide links such as privacy policies, terms of use, vendor documentation, and other external content. In those cases, users can sometimes reach the full Chrome browser experience.

In our testing, it's fairly easy for users to navigate from a CCT session into Chrome itself, such as by using the menu options available from the three-dot menu or through other user flows exposed by third-party applications. Once in Chrome, users can browse beyond the intended business workflow.

 

Moombas
Moombas
Level 4.4: KitKat
August 28, 2026

Hmm, okay i think i know what you mean and saw this as well.

So, it was just an idea. So, finally you would like to have chrome in some kind of kiosk mode (which is possible on PC but not on Android).

In such case i would agree to your feature request or even extend it to, that if apps start in fullscreen or independent mode, also the authentication screens and so on should be forced into similar mode.

I think both should be available (one more likely as a “fix”, the other a real feature request) as for both scenarios are use cases possible.

    Terms & ConditionsAccessibility statement