Working of blocklisting android appsSolved

Isn’t it straightforward? If you blocklist an app, users shouldn’t be able to use it. Basically, it’s blocked for them. 

Yeah, I get the basic idea. But there are different device types and enrollment methods, right? Samsung knox devices, Android Enterprise device owner, profile owner, and normal Android enrollment. Does the behavior change based on that? 

Hey @_janet,

Thanks for reaching out.

You’re right, app blocklisting for Android behaves differently based on the device type and the enrollment method used. Here’s a quick rundown.

1. Samsung Knox devices:
   • Blocklisted apps are prevented from being installed or updated from the Play Store.
   • If an app was already installed before it was blocklisted, it will not be removed or hidden, and users can still access it.
   • In short, blocklisting on Knox devices stops new installs and updates, but does not remove existing apps.
2. Android Enterprise – Device Owner mode:
   • Blocklisted apps are hidden if already installed.
   • Users are also blocked from downloading blocklisted apps from the Play Store.
3. Android Enterprise – Profile Owner mode:
   • Only work profile apps are affected.
   • Blocklisted work apps are hidden within the work profile, while personal apps are not impacted.
4. Generic enrollment for non-Knox devices:
   • Blocklisting or allowlisting does not hide or block apps on the device.
   • Instead, the device is marked as non-compliant when a blocklisted app is detected.
   • If email notifications are enabled under Admin > Alert Profile, the admin is notified.

Hope this clears up how blocklisting works depending on the device and how it’s enrolled. Let me know if you have any other questions.

Cheers,
Eden Pierce
Hexnode UEM