Create an Android Default App and Intent Handling Policy

The Default App & Intent Handling policy sets an approved managed app as the default handler for selected Android activities, such as opening web links or dialing phone numbers. When a matching activity occurs, Android opens the configured app automatically instead of displaying the Open with app chooser. This policy works for devices running Android 6.0 and later.

Do not configure this policy and defaultApplicationSettings for the same intent domain. Do not use this policy for a kiosk or dedicated-device launcher. Use JumpCloud’s Kiosk Mode Policy for that use case.

Prerequisites

• Devices must be enrolled in Android EMM. See Set Up Android EMM.
• The selected app must be installed, deployed to the target device, and able to handle the configured action and categories. See Add and Manage Android Devices and Users: Enroll Your Personal Android Device.

Considerations

• On work profile devices, the policy applies within the work profile. On fully managed devices, it applies across the managed device.
• Removing a rule returns matching activities to Android’s normal app-resolution behavior.
• No action is needed on the device to activate this policy after you save and assign it.

Creating the Policy

To create a Default App & Intent Handling policy for Android devices, do the following:

Selecting the Policy Template

1. Log in to the JumpCloud Admin portal.

Important

If your data is stored outside of the US, check which login URL you should be using depending on your region. If your organization uses LDAP, RADIUS, or requires firewall allow list configuration, the Fully Qualified Domain Names (FQDNs) will also be region specific. See JumpCloud Data Centers for the URLs, FQDNs, and IP addresses.

2. Go to Device Management > Policy Management. The Policy Management page is displayed.
3. On the Policy Management page, click +Add New.
4. Select Device Policy to assign the policy to devices and device groups. On the New Device Policy page:
   • Select the Android tab.
   • Search and select Default App & Intent Handling, then click Configure. The Details tab of the policy is displayed.
   • On the Details tab, configure the required policy configuration settings.
   • (Optional) In the Policy Name field, enter a new name for the policy or keep the default. Policy names must be unique.
   • (Optional) In the Policy Notes field, enter details such as creation date of the policy, and information on testing and deployment of the policy.

Supported Enrollment Types

Enrollment type	Supported
Work Profile (Personal device)	Yes
Work Profile (Company-owned device)	Yes
Fully managed device	Yes
Dedicated device	No

Configuring Default App Rules

You can add, edit, duplicate, reorder, and delete rules. The UI warns about duplicate or overlapping rules.

Field	Description
Rule Name	Required. Unique within the policy. JumpCloud admin label only. Not sent to Google.
Preferred Application	Required. Managed Android app from JumpCloud Software Management.
Activity Selection	Automatically select activity sends the app package name and lets Android Device Policy choose the activity. Specify activity lets you provide the activity class or component.
Activity Class	Required only when Specify activity is selected. Example: com.company.securebrowser/.MainActivity.
Actions	Required. One or more intent actions. If multiple are set, a match occurs when the incoming action equals any configured value.
Categories	Optional. Zero or more intent categories. All categories required by the incoming intent must be in the rule.

Actions

Label	Android value
Open or view content	android.intent.action.VIEW
Dial a phone number	android.intent.action.DIAL
Send content	android.intent.action.SEND
Open the device home screen	android.intent.action.MAIN
Custom action	Custom value

Categories

Label	Android value
Default handler	android.intent.category.DEFAULT
Web-link capable	android.intent.category.BROWSABLE
Home application	android.intent.category.HOME
Custom category	Custom value

Example Configurations

Opening Web Links in a Corporate Browser

1. Deploy two browser-capable apps, including a corporate browser.
2. Set Preferred Application to the corporate browser, Action to VIEW, and Categories to DEFAULT and BROWSABLE.
3. From a managed email or messaging app, tap an HTTPS link.

Expected result: the corporate browser opens with no app chooser.

Using a Corporate Dialer

1. Deploy the corporate dialer alongside another dialer-capable app.
2. Set Preferred Application to the corporate dialer, Action to DIAL, and Category to DEFAULT.
3. Tap a telephone link or start a dial action from a managed contacts app.

Expected result: the corporate dialer opens with the number populated and no app chooser.

Updating or Removing a Rule

1. Apply a web-link rule for Browser A and verify it.
2. Edit the rule to use Browser B and verify matching links open in Browser B.
3. Delete the rule or unassign the policy.

Expected result: Android returns to normal intent resolution. If multiple capable apps are installed and no user default exists, the app chooser appears again.

Applying the Policy

• (Optional) Select the Device Groups tab. Select one or more device groups where you want to apply this policy. For device groups with multiple OS member types, the policy is applied only to the supported OS.
• Or, select the Devices tab. Select one or more devices where you want to apply this policy.
• Click save. A success message is displayed indicating the completion of policy creation.

Viewing Policy Status

1. Select the Status tab.
2. To see the last Result Log for a device where this policy is applied, click view.

note

If any errors occur, they're listed in Exit Status. If you have an Exit Status of 0, no errors occurred when applying or enforcing this policy.

Validation and Error Handling

• A rule cannot be saved without a name, preferred application, or action.
• Custom action, category, and component-name values are validated.
• The UI warns on overlapping rules and warns or prevents conflicts with defaultApplicationSettings for the same intent domain.
• Android Management API errors and device non-compliance details are shown to the administrator.

tip

For this policy to take effect, you must specify a device or a device group.