Muting Esper Agent notifications during and after provisioning using Blueprint JSON config

Android

Esper Agent and related applications generate system notifications during and after device provisioning. If these notifications are disruptive in your production or lab environment, you can suppress them using Blueprint JSON configuration while preserving critical notifications like bug report prompts.

Before you begin

You'll need:

• Access to the Esper Console with permissions to edit Blueprints
• An existing Blueprint applied to your device group(s)
• Basic familiarity with JSON syntax

This configuration suppresses notifications from Esper Agent, Esper Helper, and Esper Remote Viewer only. Other notifications—including bug reports and system alerts—will continue to function normally.

How to add notification suppression to your Blueprint

1. In the Esper Console, navigate to Blueprints → [Your Blueprint Name] → Android Settings → Global Android Settings JSON.
2. In the Global Android Settings JSON field, insert or merge the following JSON configuration:

   {
    "commands": [
    {
    "type": "Simple",
    "command": "SET_APP_NOTIFICATIONS",
    "commandId": "Hide Esper Agent Notifications",
    "packageName": "com.esper.app.Esper Agent",
    "notificationsState": "DISABLED"
    },
    {
    "type": "Simple",
    "command": "SET_APP_NOTIFICATIONS",
    "commandId": "Hide Esper Helper Notifications",
    "packageName": "com.esper.app.helper",
    "notificationsState": "DISABLED"
    },
    {
    "type": "Simple",
    "command": "SET_APP_NOTIFICATIONS",
    "commandId": "Hide Esper Remote Viewer Notifications",
    "packageName": "com.esper.app.remotemonitor",
    "notificationsState": "DISABLED"
    }
    ]
   }

3. If your Blueprint already contains a commands array, merge these three command objects into your existing array instead of creating a second commands key.
4. Save the Blueprint.
5. Navigate to Devices & Groups → [Your Device Group] → Blueprint → Apply to publish the updated Blueprint to your devices.

How to verify the configuration is working

1. Wait for the Blueprint to fully converge on your devices. Check Devices & Groups → [Device Name] → Blueprint Status to confirm all commands have completed successfully.
2. On a provisioned device, pull down the notification shade.
3. Confirm that no notifications appear from Esper Agent, Esper Helper, or Esper Remote Viewer. Notifications from the Android system or other applications should still appear normally.

Troubleshooting

Esper notifications are still appearing after Blueprint convergence:

• Verify the Blueprint has fully converged by checking Devices & Groups → [Device Name] → Blueprint Status. Ensure there are no pending or failed commands.
• If you're using a Supervisor Plugin, check for conflicting notification policies applied at the plugin level that may override the Global Android Settings JSON.
• Confirm your device is running a current version of the Esper Agent and Esper Helper. Legacy agent versions may not support the SET_APP_NOTIFICATIONS command.

Problem affects only specific device models or manufacturers:

Gather a bug report from an affected device by navigating to Devices & Groups → [Device Name] → Bug Report, then contact Esper Support with the report, your Blueprint JSON, and the agent version details.

Important notes

• The commandId values are descriptive labels and can be customized without affecting functionality.
• This configuration only controls app-level notifications. It does not affect system sounds or notifications from non-Esper applications.
• Bug report notifications and other user-actionable alerts will continue to function normally.

Still need help?

If you've followed these steps and notifications are still appearing, or if you have questions about this configuration, contact Esper Support. Include your Blueprint JSON, device group name, and a description of which notifications are still appearing.