---
title: iOS Go Advanced Features
slug: nmdm/admin-guide/engb/vnow/ios-go-advanced-features
createdAt: 2026-09-24T14:49:10.000Z
---

Key-Value Pairs (KVPs) are simple application settings made up of a key (the name of the setting) and a value (the configuration you want to apply). In Ivanti Go for iOS, organizations use KVPs to enable or disable features and adjust app behavior without requiring an app update.

When Ivanti Go runs on organization managed iPhones or iPads, it reads these KVP settings at startup or during a check-in. The app applies the updates immediately, ensuring that configuration changes are delivered quickly, consistently, and to the correct users.

## Using KVPs in Ivanti Go App configurations

KVPs for customizing violation messages are supported on Ivanti Go app. You can configure KVPs within the Ivanti Go app settings to customise application.

### Procedure

1. Open the **Ivanti Go app** in your AppCatalog.
2. Select **Configurations**.
3. Click **Add** to create a new **Apple App Configuration**.
4. Add your KVPs manually:
   - In the **Key** column, enter the configuration key you want to customise.
   - In the **Value** column, enter the value you want enforced on devices.
5. (Optional) Upload an existing *.plist* file containing predefined KVPs you wish to apply.
6. **Save** the configuration.
7. The updated KVPs will be applied to devices during their next check-in.

### Adding a plist to a specific iOS App (for Multiple Key-Value Pairs)

Administrators can configure multiple Key-Value Pairs (KVPs) for an iOS app using app serial numbers, bundle identifiers, version details, or other metadata. This can be done efficiently by uploading a .plist file through the Ivanti Neurons for MDM console.

### Procedure

1. Go to **Apps**.
2. Open **App Catalogue**.
3. Select and open the **Specific iOS app** you want to configure.
4. Go to the App Configurations tab.
5. Select **Apple Managed App Configuration**.
6. Click the **+Add** button.
7. Enter a **Name** for your configuration.
8. Click **Use .plist**.
9. Select **Choose one of these options**.
10. Browse to your plist file, select it, and click **Open**. The system will automatically populate the configuration table with the key value pairs from the plist.
11. Choose the user group(s) or device group(s) that should receive the configuration.
12. Click **Distribute this App Config**.
13. Click **Save** to complete the process.

:::hint{type="info"}
The uploaded file must have a .plist extension. If you manually created the file (example, in a text editor), ensure that the extension is changed from *.txt* to *.plist* before uploading.
:::

## Launching Ivanti Go in Single App Mode during registration

This feature enables administrators to use key-value pairs during device registration to automatically launch the Ivanti Go for iOS in Single App Mode (SAM). When a device begins enrollment, the configured key-value pairs trigger Ivanti Go to open immediately. During this process, the user is presented with a message indicating:

Please wait while your device is being configured.

To activate this behavior, the Single App Mode configuration must be installed and explicitly targeted to the Ivanti Go for iOS before or during the registration workflow. Once enrollment is successfully completed, Single App Mode is automatically exited. The device is then released to the end user for normal operation, ensuring secure setup without restricting post registration use.

This capability supports Ivanti Mobile\@Work environments, providing a secure registration flow for supervised iOS devices.

### Setting up Zero Touch activation

To enable Zero Touch Activation for Ivanti Go, complete the following steps:

1. Set up a group that includes only devices where *Client Registered = No*.
2. Create a Single App Mode (SAM) configuration for the Ivanti Go application. Assign this configuration only to the device group created in *Step 1*.
3. Add the zero\_touch\_activation key value pair (KVP) to the Ivanti Go app configuration. Target the same device group used in the previous steps.

### configuration.

| Key                     | Value | Type    | Description                                                                                                                                                                                                                                                                                                                                                                                                         |
| ----------------------- | ----- | ------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| zero\_touch\_activation | True  | Boolean | When the value is set to true, the Ivanti Go app recognizes that it is running in Single App Mode (SAM) through the SAM configuration. The SAM configuration launches the Ivanti Go app, while this value acts as an additional setting that enables the app to function correctly in SAM mode. After successful enrollment, the device exits Single App Mode and becomes available to the end user for normal use. |

## Enabling the Return to Service Button in Ivanti Go (iOS 18+)

The **Return to Service** feature allows the device to automatically re-enroll once data is wiped, reducing the need to manually re-enroll the device after a wipe.

Administrators can enable or disable the Return to Service button using a configurable Key Value Pair (KVP). When the KVP is deployed to Ivanti Go as part of the app configuration:

- The Return to Service option becomes visible to the end user.
- The user can initiate the reset process directly from Ivanti Go.
- The device performs an Apple managed Return to Service reset.
- Management profiles and required apps remain intact.
- The device completes its re-provisioning flow and becomes ready for reuse.

This feature is supported on Ivanti Go for iOS, iOS 18 and later devices enrolled in DEP mode.

### configuration.

Add the following KVP to the Ivanti Go managed app configuration in Ivanti Neurons for MDM:

| Key                    | Value | Description                                                                                                      |
| ---------------------- | ----- | ---------------------------------------------------------------------------------------------------------------- |
| ReturnToServiceEnabled | true  | Enables the **Return to Service** button in Ivanti Go. When set to false or omitted, the feature remains hidden. |

## Disabling screenshot protection on the SAML authentication screen

The Ivanti Go for iOS include built in screenshot protection to enhance security during device registration. By default, the registration with SAML authentication screens block:

- Screenshots
- Screen recordings
- Screen sharing

This protection ensures that sensitive authentication data - such as usernames, passwords, and SAML based login content cannot be captured or shared without authorization.

Administrators can disable screenshot protection on managed devices using a KVP configuration. When this configuration is applied, the Ivanti Go app will allow screenshots and recordings only on the SAML Authentication screen, while maintaining all other security mechanisms throughout the app.

### configuration.

To disable screenshot protection for the SAML authentication screen, apply the following KVP to the Ivanti Go app configuration in your MDM:

| Key                              | Value | Description                                                                                                                                                                  |
| -------------------------------- | ----- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| SCREENSHOT\_PROTECTION\_DISABLED | True  | Disables screenshot, screen recording, and screen sharing protection on the SAML Authentication screen. When omitted or set to False, protection remains enabled by default. |

## KVPs for customizing policy violation messages

These KVPs enable administrators to customise the messages sent to end users when Policy Violations are detected.

These KVPs for customization describes the KVPs and violation types available to administrators to customise Ivanti Go for iOS app behavior. These KVPs define app behavior such as providing detailed notifications to device users and export contacts from Ivanti Go for iOS.

The violation types are not mutually exclusive. If there are a set of violations, then a list of messages will be shown in the Ivanti Go for iOS.

| Key Value Pairs (KVP)                         | Default Messages                                                                                                                                                                             |
| --------------------------------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| compliance.message.COMPROMISED                | - Your device has been compromised because it has been jailbroken. Please properly return your device to a non-jailbroken state or contact your administrator for help resolving this issue. |
| compliance.message.DATA\_PROTECTION\_DISABLED | - Corporate access has been disabled for data protection. Please contact your administrator for help resolving this issue.                                                                   |
| compliance.message.OUT\_OF\_ CONTACT          | - Your iOS device is out of contact. Please contact your administrator for help resolving this issue.                                                                                        |
| compliance.message.APPS                       | - Your device is missing apps that are required and/or it has apps that aren’t allowed. Please add/remove necessary apps or contact your administrator for help resolving this issue.        |
| compliance.message.MDM\_DISABLED              | - Your device is out of compliance because MDM capability has been deactivated. Please re-enroll your device, or contact your administrator for help resolving this issue.                   |
| compliance.message.ROAMING                    |                                                                                                                                                                                              |
| compliance.message.generic                    | - Corporate access has been disabled for an unspecified reason. Please contact your administrator for help resolving this issue.                                                             |
| compliance.message.header                     | Your device is out of compliance for the following reason(s):<br />When the violation type is CUSTOM or CUSTOM\_NOTIFY\_ONLY, the system displays standalone messages without a header.      |
| compliance.message.CUSTOM                     | An action may be required on your device. Please contact your admin as needed.                                                                                                               |
| compliance.message.CUSTOM\_NOTIFY\_ONLY       | Your device is out of compliance, and a notification has been sent. Please refer to the notifications tab or your email for details.                                                         |

:::hint{type="info"}
If the violation types list does not include any violation with a mapped message, but it includes at least one violation without a mapped message, then display the default message:
:::

- Corporate access has been disabled for an unspecified reason. Please contact your administrator for help resolving this issue.

:::hint{type="info"}
If the messages list contains at least one violation message, display the following header above the list:
Your device is out of compliance for the following reason(s):
:::

:::hint{type="info"}
If you do not want to change a default message, do not include a key-value pair (KVP) for it. Only define KVPs for the messages you intend to modify.
:::

## Configure default browser and email clients using Managed App Configuration

Key Value Pairs (KVP) enable administrators to configure which browser and email client **Ivanti Go** uses when opening web links and composing emails via Managed App Configuration.

As an administrator, you can use Managed App Configuration KVPs to control how links are handled within the **Support** tab:

| Key                               | Value                                                                      | Type    | Description                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                         |
| --------------------------------- | -------------------------------------------------------------------------- | ------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| default\_browser                  | safari, edge, chrome, firefox, brave, opera, webatwork, duckduckgo         | String  | Browser Ivanti Go uses to open web links in the Support tab. http/https links are redirected to the configured browser’s scheme. **Default if not configured**: system default browser.                                                                                                                                                                                                                                                                                                                             |
| Allow\_browser\_fallback          | true, false                                                                | Boolean | **Behavior when default browser is not installed**:<br />**True**: Falls back to default system browser.<br />**False**: Link not opened, user sees “\<Browser> not installed” alert.<br />**Default if not configured**: True                                                                                                                                                                                                                                                                                      |
| restrict\_log\_sharing\_to\_email | true, false                                                                | Boolean | Whether log/support sharing is restricted to email only (using default\_email).<br />Auto-attaching logs works with Email+ and Native mail<br />Works with **allow\_email\_fallback**.<br />**True**: sharing to email only.<br />**False**: standard sharing options available.<br />**Default if not configured**: false.                                                                                                                                                                                         |
| default\_email                    | nativemail, outlook, gmail, yahoo, citrixmail.emailplus, spark, protonmail | String  | Email Client Ivanti Go uses to compose mails from mailto links in Support tab. mailto is transformed into the client’s composing URL **Default if not configured**: Default mail application . Dual role in link resolution and log sharing when default\_email client is not installed.                                                                                                                                                                                                                            |
| Allow\_email\_fallback            | True, False                                                                | Boolean | **Behavior when default email is not installed**.<br />**True**: Email composition falls back to the default mail application if the configured email client is not installed, and log sharing can use an alternate delivery method.<br />**False**: Email composition is blocked, and users see a “**Not Installed**" alert if the configured email client is unavailable. Log-sharing restrictions are enforced with no fallback option.<br />**Default if not configured**: true. (fallback behavior is enabled) |
