Configure Mobile Notification Controls via MDM

Table of Contents

Create and Manage HIP Profiles for the Prisma Agent

Configure Mobile Notification Controls via MDM

Deploy custom keys in your MDM profile to control which background notifications the Prisma Agent sends on managed iOS and Android devices.

Where Can I Use This?	What Do I Need?
Prisma Agent on iOS (Managed Devices) Prisma Agent on Android (Managed Devices)	Prisma Agent 26.4 MDM solution (such as Jamf or Microsoft Intune) Managed device enrollment

Mobile notification controls let you tailor the Prisma® Agent notification experience to match your organization's operational needs. Different deployment scenarios call for different notification strategies: some organizations want full visibility across all categories, while others prefer to limit interruptions for users who connect automatically in the background. Rather than applying a single all-or-nothing setting, you can configure each notification category independently through mobile device management (MDM). Each category can be set to active, suppressed, or user-adjustable, so you preserve the alerts that require user action while reducing the ones that don't.

The Prisma Agent organizes mobile notifications into three configurable categories:

Connection Failure — alerts users when the agent cannot establish or maintain a connection
User Sign-in is required — covers events that require user intervention, including SAML and LDAP authentication prompts, certificate selection, and captive portal prompts (iOS only)
Session Extension — informs users when their session is nearing expiration and gives them the opportunity to extend it before they are disconnected

For each category, you set one of three values in the MDM profile:

enabled — the notification is active and users cannot toggle it
disabled — the notification is hidden from users entirely
user_controlled — the notification is on by default, and users can toggle it off in the Notification Controls section of the Prisma Agent app

Any category you do not configure defaults to enabled. The Prisma Agent reads the MDM configuration on every new connection.

Notification controls apply to background notifications only. When the Prisma Agent app is in the foreground, all notification types are displayed regardless of your configuration. HIP notifications are always enabled and are not subject to these controls. On Android, two notifications cannot be suppressed due to OS VPN compliance requirements: the alert that the VPN service started, and the notification to restart the app when the app container is killed. On unmanaged devices, users can view the Notification Controls section of the app but all toggles appear grayed out — no MDM configuration is applied.

In your MDM solution, open the VPN or app configuration profile for the Prisma Agent.

Add the custom configuration keys for each notification category you want to control:

Key	Values	Default
notification_connection_failure	enabled \| disabled \| user_controlled	enabled
notification_user_action	enabled \| disabled \| user_controlled	enabled
notification_session_extension	enabled \| disabled \| user_controlled	enabled

Any key you omit defaults to enabled.

(iOS) Add the keys to the custom data section of the per-app VPN or global VPN profile. The Prisma Agent parses them from the VPN payload on each connection.
(Android) Add the keys to the managed app configuration section of the Prisma Agent app profile.
Deploy the updated profile to the target managed devices.

On the next connection, the Prisma Agent reads the MDM configuration and applies the notification settings. Users can view and manage their settings in Notification Controls (iOS) or Notification Controls (Android).

Create and Manage HIP Profiles for the Prisma Agent

MDM Posture Checks for Prisma Agent

Prisma Agent Docs

Configure Mobile Notification Controls via MDM

Prisma Agent Docs

Configure Mobile Notification Controls via MDM

Activation and Onboarding

SASE

Cloud-Delivered Security Services

Network Security

Endpoints

Visibility & Monitoring

Best Practices

Experts Corner