Block apps in Google Admin and managed Google Play
Google spreads app control across four screens, and each device type gets different powers. This guide shows where to block apps in Google Workspace, which mode each screen offers, how to test a change, and where a category blocklist saves you hours.
Where to block apps in Google Workspace
Most confusion comes from one fact: Google Admin is not one MDM screen. App rules for Chromebooks sit under Chrome, rules for phones sit under Mobile and endpoints, and data access rules sit under Security. Use this map to find the right place first.
| Device or need | Console path (check your current console) | Modes offered | Block one app by ID? |
|---|---|---|---|
| Android apps on Chromebooks | Devices > Chrome > Apps & extensions > Users & browsers | Installation policy per app: Allow install, Force install, Force install + pin, Block | Yes, by Google Play app, using the Android package name |
| Android on/off for Chromebooks | Additional app settings > Android apps on Chrome Devices | Allow users to install Android apps, or not | Not applicable, it switches Google Play on or off |
| Android phones and tablets | Devices > Mobile & endpoints > Settings > Android > Apps and data sharing > Available apps | Only allowed apps (allowlist) or the default | No blocklist; you allow apps on the Web and mobile apps list |
| App list for phones | Apps > Web and mobile apps > Add app | Available or Force install, per group or organizational unit | Adds approved apps only |
| iPhone and iPad | Devices > Mobile & endpoints > Settings > iOS > Apps and services > App installation | Allow users to install apps, on or off | No; supervised company-owned devices only |
| Third-party apps reading Google data | Security > Access and data control > API controls | Trusted, Limited, Specific Google data, Blocked | Blocks data access, not installation |
Allowlist or blocklist: which modes Google gives you
Google leans towards allowlists. That is safe, but it makes every new app request a ticket. Knowing which screens accept a blocklist tells you where a category file can do the heavy lifting.
Block all apps, admin manages allowlist
- Users see and install only the Android apps you allowed.
- The only Android mode for education domains on Chromebooks.
- The phone equivalent is the Available apps setting set to Only allowed apps.
- Allowlisting stops users switching to secondary accounts in managed Google Play.
- Every request needs a quick review before you allow it.
Allow all apps, admin manages blocklist
- Users can install any Google Play app except the ones you block.
- Offered for Android apps on Chromebooks in business domains.
- Not offered to education domains.
- Needs a long, current block list by category to work well.
- New clone apps slip through unless your list keeps up.
Block Android apps on Chromebooks, step by step
These steps cover Google Play apps running on ChromeOS. Chrome extensions use the same Apps and extensions screen but are a different kind of app; see our page on Chromebook apps and extensions for those.
- Accept the Play terms and add Android Enterprise. A super administrator must accept the Google Play terms, and Android Enterprise must be listed under Billing > Subscriptions. Without both, Android apps never appear.
- Turn Android apps on for the right users. In the additional app settings, open Android apps on Chrome Devices and allow users to install Android apps. Apply it to a test organizational unit first.
- Pick the allow or block mode. Business domains can choose Allow all apps, admin manages blocklist. Education domains will only see the allowlist mode.
- Add the apps you want to control. On the Users & browsers tab, use Add from Google Play, search for the app and open it. The detail panel shows the package name, which is what our files list.
- Set the installation policy. Choose Block for apps you do not want, Allow install for approved apps, or Force install for apps every student needs. Force install + pin also places the app on the shelf.
- Save, then wait and test. Changes usually apply within minutes but can take up to an hour. Sign in as a test user and confirm the Play Store shows only what it should.
Limit Android phones and tablets to approved apps
For Android phones, Google endpoint management works on an approved list. You add apps under Apps > Web and mobile apps, then tell devices to offer only those apps.
- Set up advanced mobile management. The Available apps setting and blocking unmanaged installs both require it, plus the Mobile Device Management administrator privilege.
- Build the approved list. Go to Apps > Web and mobile apps, click Add app, then Search for apps. Choose the users or organizational units, then set the access method to Available or Force install.
- Switch on the allowlist. Open Devices > Mobile & endpoints > Settings > Android, then Apps and data sharing > Available apps, and select Only allowed apps. Save, or Override for a child unit.
- Handle what is already installed. The switch blocks new installs only. Apps already on the device stay, so clean them up or re-provision devices that matter.
- Allow up to a day. Google says this change can take up to 24 hours, though it is usually faster. Test on one device before widening the scope.
Personal phones with a work profile
Your list governs the work side only. Personal apps stay outside your control, which is by design. See the Android work profile guide for what you can and cannot block there.
Phones and tablets you own
The allowed list applies to the whole managed device. For shared tablets, pair it with force-installed apps so every learner gets the same set.
iPhones and iPads in Google Admin
Google endpoint management can secure iPads and iPhones, but its app controls are narrow. Know the limits before you promise a principal that a game will vanish from every iPad.
App installation switch
Under the iOS settings, Apps and services > App installation, untick Allow users to install apps. Users lose the App Store and can install only the apps you allow through Google's device policy app.
Managed iOS apps
When adding an iOS app you can make it a managed app and remove it with the profile. Making iOS apps managed requires advanced mobile management.
App access control
You can stop a named app from reaching Gmail, Drive or other Google services. The app still opens; it just cannot use your Workspace data.
How an AppBlockList file plugs into Google Admin
Our blocklists ship as Android package lists, iOS bundle ID lists, CSV files with every column and Apple configuration profiles. In Google Admin, each one has a clear job.
Feed the blocklist
In Allow all apps mode, take the Android package file for the categories you chose, such as Gambling or VPN / Proxy / Anonymizers, and set each app to Block.
Vet allowlist requests
Before you allow a requested app, look it up in the CSV or with our app category lookup. If it sits in a blocked category, the answer is ready.
Use the profile file
For iPads managed elsewhere, the .mobileconfig file carries the same categories as bundle IDs, so both fleets follow one policy.
Example lines from an Android package file: TikTok, Snapchat, Roblox, NordVPN, Turbo VPN, ChatGPT, DraftKings Sportsbook and Tinder. Real files hold every app in the categories you pick, refreshed monthly.
Test before you roll out
A ten-minute test on one device saves a morning of help desk calls. Run through this list with a test account in its own organizational unit.
- Create a test organizational unit and put one test user and one device in it.
- Confirm group settings do not override it: groups beat organizational units.
- On the Chromebook, open the Play Store and search for a blocked app by name.
- Try a force-installed app: it should appear without the user doing anything.
- On a phone, open the work Play Store and check only approved apps are listed.
- Install an app before the policy, then apply it, and note that it stays.
- Check an iPad with App installation off: the App Store icon should be gone.
- Write down the time of each change so you can judge how long sync took.
Common errors and how to fix them
These are the problems admins hit most often when they block apps in Google Admin. Each one has a simple cause.
Android apps do not show up on Chromebooks at all
The Allow all apps option is missing
A blocked app still opens on a phone
I deleted the app from the list but students still use it
Settings look right but one class behaves differently
Our private app is not visible yet
The iPad App Store switch has no effect
Questions admins ask
Where do I block apps in Google Workspace?
Can I block a single iOS app by bundle ID in Google Admin?
Why is the Allow all apps option missing on our school Chromebooks?
Does switching Android devices to only allowed apps remove apps already installed?
Is Google Workspace app access control the same as blocking an app?
How long do Google Admin app changes take to reach devices?
Want to check an app before you decide? Our package name lookup gives a few free lookups a day, and the VPN and proxy apps list shows the category most schools block first.
Stop typing package names one by one
Pick the categories, get one file per platform, and let the monthly update catch the new clones. One plan covers a school or business, another covers districts and IT providers.
Google, Google Workspace, Google Admin, Google Play, Android, ChromeOS, Chromebook, Gmail and Google Classroom are trademarks of Google LLC. Apple, iPhone, iPad and App Store are trademarks of Apple Inc.
Microsoft Intune is a trademark of Microsoft Corporation. Jamf Pro is a trademark of Jamf. TikTok is a trademark of ByteDance Ltd. Snapchat is a trademark of Snap Inc. Roblox is a trademark of Roblox Corporation.
NordVPN, Turbo VPN, ChatGPT, DraftKings and Tinder are trademarks of their respective owners. Names are used only to identify the products discussed. AppBlockList is not affiliated with, sponsored or endorsed by these companies.