All installed apps not visible to users — configure Blueprint app visibility

Android

When a device group is managed under a Blueprint with restrictive app visibility settings, end users see only a subset of installed apps on their devices instead of the full list of available applications.

Why this happens

Blueprints control which apps appear on the device launcher. If individual app states are set to Hide, or if the launcher mode restricts visibility, apps that are installed on the device will not appear to the user. Both conditions can apply simultaneously, so both may need to be addressed.

Option A: Set all preloaded apps to visible in the Blueprint

Open the Esper Console and navigate to Blueprints.
Select the Blueprint applied to your target group and open the Apps section.
Set the app state to Show for all preloaded and system apps. Use the bulk state option to apply this across all apps at once rather than updating each entry individually.
Save and publish the updated Blueprint.
Apply the Blueprint to the group by navigating to Devices & Groups → [Group Name] → Blueprint and selecting Apply. This pushes the updated visibility settings to all devices in the group.

Verify: Open the launcher on a test device in the group. All installed apps, including preloaded system apps, should be visible within 5 minutes of the Blueprint applying successfully.

Option B: Change the launcher mode to unrestricted

If the launcher mode itself is limiting app visibility — for example, because the device is in kiosk or single-app mode — update the launcher configuration in the Blueprint.

Open the Esper Console and navigate to Blueprints.
Select the Blueprint applied to your target group and open the Launcher section.
Change the Launcher Mode from kiosk or single-app mode to a multi-app mode. Kiosk and single-app modes are designed to restrict visibility to one or a defined set of apps by design.
Save and publish the updated Blueprint.
Apply the Blueprint to the group by navigating to Devices & Groups → [Group Name] → Blueprint and selecting Apply.

Verify: On a test device in the group, confirm the standard Android launcher is active and all installed apps are accessible. This should be reflected within 5 minutes of a successful Blueprint sync.

Important considerations before applying changes

These settings apply at the group level. Every device in the group will inherit the same app visibility configuration.
If specific devices require different visibility rules, move those devices to a separate group with its own Blueprint.
Making all system and preloaded apps visible will expose device management utilities and system tools to end users. Review this with your team before applying to a production fleet.

If this doesn't resolve it

If apps remain hidden after applying the updated Blueprint, check the following before contacting support:

Devices are offline: Blueprint updates are not delivered to offline devices. Navigate to Devices & Groups → [Device Name] → Activity Feed to confirm the device is connected and has received the latest Blueprint.
Specific system apps are still hidden: Some apps may be restricted at the OEM firmware level, independent of Esper configuration. Verify whether the app is visible on a factory-reset device outside of Esper management.
Blueprint inheritance conflict: If the group is nested under a parent group, a conflicting Blueprint applied at the parent level may be overriding your settings. Check the parent group's Blueprint configuration in Devices & Groups.

If the issue persists, contact Esper Support. Include a screenshot of the Blueprint's Apps and Launcher sections, your group ID, and the device serial number of an affected device showing the issue.

Still need help?

If the steps above don't resolve the issue, submit a support ticket with your device model, Android version, Esper Agent version, and a description of what you've already tried — this helps the support team investigate without a follow-up.