Helperbird Declarative MDM Setup for iPhone and iPad

Declarative device management (DDM) can deliver Helperbird settings directly to its Safari extension on supported iPhones and iPads. This route avoids the periodic containing-app refresh required by legacy managed app configuration.

It uses Apple's ManagedApp configuration, a private settings asset and an extension configuration entry. It is not a standalone .mobileconfig file you install by tapping a download.

Before You Start

• iOS or iPadOS 18.4 or later, for Helperbird's ManagedApp reader.
• An MDM deployment that supports ManagedApp data assets and ExtensionConfigs. General DDM support alone is not enough.
• A signed Helperbird build containing the 2026.9.6 managed-settings support.
• The Safari extension's bundle ID and signing team ID, verified for your release.
• A managed app installation and a way to deliver its declarations through your MDM.

App installation and Safari extension enablement are separate from these settings. Confirm support with your deployment contact and pilot the signed app on enrolled devices before a fleet rollout.

Step 1: Create the Settings Asset

1. Open the Helperbird policy builder.
2. Choose Safari on iPhone & iPad.
3. Select Declarative MDM: plist + extension fragment.
4. Enable organization control and choose the settings to deliver.
5. Download the settings plist.

The settings use the same typed dictionary as legacy AppConfig. isAdminControl must be true; subKey is optional. For all available fields, see the Apple managed settings reference.

Publish the plist through your MDM's private data asset process, using declaration type com.apple.asset.data and content type application/x-plist. Your MDM supplies the asset identifier and its delivery details.

A plist containing a subscription key must not be hosted at a publicly readable URL. Do not substitute a public website download link for your MDM's private asset setup.

Step 2: Target the Safari Extension

Enter the private data asset identifier and verified signing team ID in the builder. Select Download DDM fragment.

The resulting fragment has this shape. TEAMID1234 is an example placeholder, not Helperbird's release team ID:

{
  "ExtensionConfigs": {
    "com.helperbird.Helperbird.Extension (TEAMID1234)": {
      "DataAssetReference": "com.school.helperbird.settings"
    }
  }
}

Replace the team ID with the one from the signed release, and the asset reference with the declaration identifier your MDM created. The composed identifier includes a space before the parentheses.

Add this fragment to the managed app's com.apple.configuration.app.managed declaration using your MDM's workflow. Retain the declaration's existing app installation, identity and asset setup. The fragment is not a complete declaration.

Target the Safari extension under ExtensionConfigs. Supplying only AppConfig to com.helperbird.Helperbird does not feed this direct extension route.

Apple documents the relationship between the managed app, configuration assets and extension identifiers in Configuring managed apps and extensions (opens in a new tab).

Step 3: Deploy and Verify

1. Assign the app declaration and its private asset to a test iPhone or iPad.
2. Check declaration status in your MDM, including asset delivery.
3. Enable Helperbird in Safari if it is not already enabled.
4. Open a normal website and verify one configured feature.
5. If the policy supplies a subscription key, check Pro status while online.
6. Change a feature without changing the key and confirm that the new setting arrives.

The extension observes ManagedApp updates and refreshes policy periodically while its background runs. Sleep, suspension and network loss can delay delivery. Unlike legacy AppConfig, this route does not need the containing app's weekly refresh.

Change or Remove a Declaration

Use your MDM's declaration update process for policy edits and key rotation. To release management, deliver isAdminControl: false in the settings dictionary or remove the configuration through that same route. Verify the result on a connected test device.

An empty subKey releases managed licensing while keeping other feature settings active. Removing management restores personal settings and any personal subscription.

Once this installation has received DDM configuration, Helperbird continues to treat DDM as authoritative across restarts. It does not fall back to an old legacy AppConfig key when the declaration disappears.

If you must return to legacy AppConfig, arrange a reinstall or re-enrollment pilot with your deployment team. Preserve user work first and confirm the migration steps with support. Do not attempt the switch by pushing both configurations at once.

Troubleshooting

No settings arrive: verify OS support, the signed app version, asset delivery and the composed extension identifier.

Your MDM cannot accept the fragment: it may support DDM without exposing ManagedApp extension configuration. Ask your MDM provider about ExtensionConfigs, or use the legacy AppConfig route on a suitable installation.

Settings validate in the builder but do not apply: the builder checks file structure. It cannot check enrollment, signing, asset permissions or subscription validity.

An offline device keeps old restrictions: delivery failure is not a confirmed policy removal. Bring the device online and check that it receives the updated declaration.

Need Additional Help?

Contact Helperbird support with your app version, OS version and MDM. Share configuration structure with subscription keys removed.

For MDM implementation details, see Apple's ManagedApp configuration documentation (opens in a new tab) and Jamf's ManagedApp and Blueprints guide (opens in a new tab).