Introduction
If your Macs are already enrolled in Microsoft Intune, you can push the Level agent to them without touching each machine. This guide walks through the three pieces of a working deployment:
The PKG app that installs and registers the agent.
A PPPC profile that configures privacy permissions for Level on macOS.
A macOS service account for Level-managed FileVault actions on Apple Silicon and Intel Macs, and for restart-requiring macOS system updates on Apple Silicon.
ℹ️ NOTE: Set up the service account on Macs where you plan to use Level-managed FileVault actions, or restart-requiring macOS system updates on Apple Silicon. It is not an Apple-Silicon-only account. See macOS Service Account for the feature and architecture requirements.
⚙️ PREREQUISITES
Macs enrolled in Microsoft Intune, with access to the Microsoft Intune admin center
A Level account with permission to add devices
The Level install key for the group you want devices to land in (get it from Add new device → macOS in Level)
For the service account step: an existing local macOS administrator on each Mac that holds a SecureToken, and root privileges to run the setup
Install Level on macOS via Intune
Step 1: Download the macOS installer from Level
In Level, open the Device Listing and click Add new device.
Select macOS from the operating system dropdown.
Open the Installer tab.
In the architecture dropdown, select ARM64 for Apple Silicon or x64 for Intel.
Optionally select a device group so the install key includes the group ID.
Click Download installer to save the PKG.
🖥️ PLATFORM NOTE:
Apple Silicon (M1/M2/M3): Download the ARM64 package. Review the service account requirements in Step 4 for macOS updates and FileVault actions.
Intel: Download the x64 package. The PKG is architecture-specific, so a package built for one architecture won't install on the other. Review Step 4 if you use Level-managed FileVault actions.
⚠️ WARNING: Because each PKG is architecture-specific, an ARM64 package won't run on Intel Macs and vice versa. If you manage both, create a separate Intune app per architecture and scope each assignment to the matching devices.
Step 2: Create the PKG app in Intune
In the Intune admin center, go to Apps → macOS → Add.
For App type, select macOS app (PKG), then click Select.
Click Select app package file, browse to the PKG you downloaded, and click OK.
On the App information page, set the Publisher (for example,
Level) and choose a Category such as Computer management. Click Next.
Add the post-install script
Intune runs the PKG with a plain installer -pkg, which installs the agent but does not register it with your Level account. The post-install script is where registration happens, using your install key.
In Level, open Add new device, select macOS, and open the Installer tab. Confirm that you've selected the group you want the Macs to join.
Find the command below Download installer. Copy only the portion after
&&, beginning withsudo level -k. This is the registration command referenced in this guide, and it includes your install key.Paste that portion into Intune's post-install script field, then click Next.
Intune installs the PKG separately, so leave out the initial sudo installer -pkg … -target / && portion.
⚠️ WARNING: The install key links new devices to your Level account and (if you selected a group) the target group. Treat the script as sensitive and limit who can read the Intune app configuration.
Set requirements and detection rules
On the Requirements page, set the minimum operating system to match the oldest macOS you actually support. Level supports macOS 11 (Big Sur) and later. Click Next.
On the Detection rules page, configure Intune to detect whether the Level agent is present:
App bundle ID:
io.level.agentIgnore app version: Yes
Click Next, review, and click Create.
💡 TIP: Level updates the agent automatically, often several times per week. Set Ignore app version to Yes so Intune checks for the Level app bundle ID instead of comparing the installed version with the version in the deployment package.
Step 3: Deploy the PPPC profile for privacy permissions
macOS blocks Level from screen recording, controlling the machine, and reading files until it's granted the matching privacy permissions. A PPPC (Privacy Preferences Policy Control) profile pushed through Intune configures managed privacy permissions.
Level publishes an official sample profile. Start there: Download Level - PPPC.mobileconfig
The profile targets the Level agent by bundle ID (io.level.agent) and Team ID (BNB82BTKXQ), and it does two things:
Configures Full Disk Access and Accessibility through MDM policy.
Allows a standard (non-admin) user to approve Screen Recording without needing admin credentials.
On macOS 27, applying the deprecated PPPC Accessibility key shows the user a notification once for each configured app. Users can disable Accessibility permissions granted by device management in System Settings. Verify effective permissions on a test Mac before deploying broadly.
⚠️ WARNING: Apple does not allow MDM to grant Screen Recording or System Audio Recording silently. The profile only removes the admin requirement. A person still has to approve Screen Recording (and System Audio, if you use audio during remote control) on each Mac the first time. Budget for that in your onboarding steps.
To deploy it through Intune:
Go to Devices → macOS → Configuration → Create → New policy.
Set Profile type to Templates, choose Custom, and click Create.
Give the profile a Name, then click Next.
On the configuration page, set a Custom configuration profile name and upload the
.mobileconfigfile. Click Next.Pick your Assignments, click Next, then Create.
Step 4: Create the macOS service account
Level-managed FileVault enable, disable, and recovery-key rotation actions use a dedicated service account on Apple Silicon and Intel Macs. On Apple Silicon, Level also uses the account for restart-requiring macOS system updates. A silent Intune installation skips the interactive account-setup prompt, so plan account setup on devices where you need these features.
The authorizing credentials must belong to an existing local macOS administrator with a SecureToken. Run service-account setup as root. An administrator identity used only to sign in to Intune does not meet the local-account requirement. See macOS Service Account for the account requirements and background.
Protect the authorizing credentials
⚠️ WARNING: Do not store the authorizing administrator password in Level custom fields or paste it into a Level automation script. Credentials can be exposed through field access, command arguments, or error output. Do not send passwords in a Support conversation.
Review the setup before scripting
Before automating account creation across your fleet, ask Level Support to review credential handling and diagnostic output for your deployment method. This guide does not provide a credential-bearing deployment script or treat an MDM's secret storage as proof that the resulting command and error output are protected.
Scope account setup to the required devices
Include Intel Macs if you use Level-managed FileVault actions. Do not skip account creation solely because a Mac is Intel. For Apple Silicon, include devices that need Level-managed FileVault actions or restart-requiring macOS system updates.
Step 5: Confirm the deployment
Sync a test Mac (System Settings → General → Device Management, or wait for the next check-in).
Confirm the agent installed and the device appears in your Level Device Listing within a few minutes.
Confirm that the PPPC profile is installed, then verify that Level has Full Disk Access and input-control permission on the test Mac. Profile installation alone doesn't confirm effective access.
Have someone approve Screen Recording on the Mac (Apple requires this by hand).
Start a remote control session on the test Mac and confirm that you can view the screen, move the pointer, and type.
On each Mac where you set up the service account, confirm it exists with
sudo /usr/local/bin/level --check-service-account. This check applies to Intel and Apple Silicon.
ℹ️ NOTE: A successful PKG installation does not establish that registration completed. If the Mac does not appear in Level, check the post-install registration result and collect the agent diagnostics described in Offline Troubleshooting. Do not infer an AV/EDR block without a detection or diagnostic evidence.
FAQ
The PKG installed but the Mac never showed up in Level. What went wrong? Confirm that the post-install registration script ran and used the intended install key. Installation alone does not confirm registration or connectivity. If diagnostics do not establish the cause, pass the results to Level Support rather than repeating registration or assuming a security-product block.
Do I need the service account at all? Set it up for Level-managed FileVault actions on Apple Silicon or Intel, or for restart-requiring macOS system updates on Apple Silicon. Account requirements depend on the feature you use, not architecture alone. See macOS Service Account.
My service account setup fails even though the admin username and password are correct. Why? One requirement is that the local administrator authorizing setup has a SecureToken, on either Intel or Apple Silicon. The exact error determines whether that is the problem. Review the SecureToken section of macOS Service Account, and share redacted diagnostics with Support if setup still fails. Do not include passwords or unredacted credential-bearing command output.
Can I deploy to Intel and Apple Silicon at once? Not with a single app. The PKG is architecture-specific, so create one Intune app for the ARM64 package and one for x64, and assign each to the matching devices. Detection rules for both apps can use the same bundle ID (
io.level.agent) with Ignore app version set to Yes, so Intune detects the Level agent's presence instead of comparing package versions.Why does a tech still have to click something for Screen Recording if the profile handles permissions? Apple doesn't allow MDM to grant Screen Recording or System Audio Recording silently. The profile removes the admin requirement so a standard user can approve it, but the approval itself is still manual. The profile configures Full Disk Access and Accessibility through MDM policy. On macOS 27, applying the deprecated Accessibility key shows a notification once per configured app, and users can disable managed Accessibility permissions in System Settings. Test remote input rather than relying on the profile's installed status.
Where do I set which group the Macs land in? Select the group when you copy the install key in Level (Add new device → macOS). The group ID rides along in the key that your post-install script uses. To land devices in different groups, use a separate key per group.
Should I store the authorizing admin password in a custom field? No. Do not use ordinary custom fields or automation source code to distribute this password. Ask Level Support to review a deployment method that protects credentials and redacts errors before you roll it out.
