Innoactive Spatial on Apple Vision Pro supports zero-touch deployment via Jamf Pro. A single Managed App Configuration delivered through Jamf provisions the license and the Innoactive Portal backend(s) your team should connect to — devices come up licensed and pre-configured on first launch, no per-device manual setup.
This article is for IT administrators rolling out Apple Vision Pro to a team or fleet.
Prerequisites
Apple Business (formerly Apple Business Manager) and Jamf Pro need to be paired so that devices enrolled via Apple Business receive apps and configurations from Jamf. If that pairing is already in place for your iPhone / iPad fleet, you can reuse it. If not, set it up first — Apple Business handles device enrollment and app assignment; Jamf delivers the Managed App Configuration that contains the Innoactive Spatial enterprise settings.
Getting your configuration file
Submit this form with your organization details. We will add Innoactive Spatial to your Apple Business account and send you a ready-to-deploy .plist artifact for Jamf Pro.
Distribute the configuration via Jamf Pro
Once you have the .plist:
- In Jamf Pro, go to Devices → Mobile device apps → Innoactive Spatial → App configuration.
- Paste the
.plistcontents we provide into the Preferences text area. It is already in Jamf Pro's expected bare-<dict>format; no editing required. - Save and scope the app to your Vision Pro device group.
Devices receive the configuration on their next MDM check-in; Innoactive Spatial picks it up on next launch.
Reference: Jamf — Managed App Configuration.
Deploying different licenses per department
A single Apple Business organization can run multiple Innoactive Spatial licenses side by side — one per department, plant, or region — even though the app is distributed privately as a Custom App B2B. The pattern is one copy of the app per department in Jamf Pro, each with its own Managed App Configuration.
Innoactive issues a separate .plist per distinct license. Submit the access request form above once per department, noting the license and configuration differences you need — we send back one artifact per department.
Once you have one .plist per department, in Jamf Pro:
- Clone the app. Go to Devices → Mobile device apps → New and search for Innoactive Spatial to add another copy. Repeat for each department that needs its own license or configuration. Multiple copies of the same privately-distributed (Custom App B2B) app are supported.
- Assign the per-department configuration. On each copy, open App configuration and paste the corresponding department's
.plist(its license and Portal backend settings) into the Preferences text area. - Scope each copy narrowly. Scope every copy to only the intended Vision Pro devices — using Jamf Pro Sites, individual devices, or static / smart groups — so each department receives only its own license and configuration.
This is the same approach Jamf uses with customers who need different configurations across regions or business units; it is a well-established setup.
Install Innoactive Spatial as a managed app
visionOS only delivers Managed App Configuration to apps installed by your MDM as managed apps. Copies installed from the App Store by individual users won't pick up the configuration. Your standard MDM app-deployment flow handles this automatically — just make sure end users don't install Innoactive Spatial themselves from the App Store outside of your MDM workflow.
Bundle IDs to allow in your MDM
If your MDM enforces an app allowlist — or your security team needs the bundle identifiers for review — these are the IDs to register:
| App | Platforms | Bundle ID |
|---|---|---|
| Innoactive Spatial | visionOS, iOS | de.innoactive.portal.visionos |
| Spatial Operator (companion control app) | macOS, tvOS, iOS, visionOS | de.innoactive.spatial.operator |
| Broadcast (screen recording) extension | visionOS, iOS | de.innoactive.portal.visionos.broadcast |
The Broadcast extension is embedded inside Innoactive Spatial; it ships and updates with the parent app and does not need a separate app deployment, but some MDMs require listing the extension's bundle ID alongside the host app.
Verifying the deployment
Once a managed device has the configuration installed and Innoactive Spatial launched:
- The app opens straight into the licensed state — no enterprise license prompt, footer shows the Enterprise chip with your organization name.
- Settings → Cloud → Enterprise shows your licensee details, expiration date, and feature list.
- Settings → Debug → Environment lists your configured Portal backends.
- Your MDM inventory shows licensing status for each device under Managed App Feedback (or your MDM's equivalent panel).