Back to top

How to enable Device Key Mapping for applications in Work Profile

Last updated July 26th, 2023

Categories:

Environment

  • Knox Service Plugin (KSP)
  • Push-to-Talk (PTT)
  • Android 11

Overview

An enterprise IT admin can associate configurable XCover and Tab Active hardware keys with business apps through KSP. This includes the ability to configure the XCover key for PTT with Microsoft Teams and to configure XCover and Top keys for key press and key release intents to specific applications.

Previously, device key mapping was only available for Fully Managed devices. With the release of version 1.2.74 of KSP, apps installed in a Work Profile now have this same key mapping ability.

How can I map hardware keys to apps in the Work Profile?

Enable the Device Key Mapping policy:

  • Work profile policies > Device Key Mapping > Enable Key Mapping.

To enable XCover key mapping for Microsoft Teams Walkie Talkie PTT:

  • Work profile policies > Device Key Mapping > Enable PTT/Side Key Mapping for Microsoft Teams set to true.

To enable key mapping for a specific hardware press action and application package for:

XCover/Active key Mapping for a specific application

or

Top Key Mapping for a specific application

  1. Set the Package Name of the application receiving the XCover key mapping actions.

  2. Set the Intent for Keypress for the intent provided by the application vendor for the XCover/Top key press.

  3. Set the Intent for Key release for the intent provided by the application vendor for the XCover/Top key release.

Additional information

For more information, please see the Knox Service Plugin Advanced Policies

Is this page helpful?