Introduction
The Level agent is a lightweight background service that checks in with your account and makes remote control, monitoring, automation, and patch management available for a device. Installing it on macOS takes a couple of minutes, with a few permission grants required after the first install.
⚙️ PREREQUISITES
A Level account with permission to add devices
Local administrator rights on the target macOS device
macOS 11 (Big Sur) or later
🎬 VIDEO
macOS Install
Opening the Install Modal
Click Add new device in the top-right corner of the Device Listing page. In the OS selector, choose macOS.
Selecting a Device Group (Optional)
Select a device group before copying your install command. The install key updates to include the group ID, so the device lands in the right group automatically on first check-in.
If you skip this, the device lands in Ungrouped — you can move it afterward.
💡 TIP: Assigning a group at install time means the device immediately picks up all group-level automations and permissions.
The Install Key
Every macOS install method uses an install key — a short token visible in the modal that links new devices to your Level account. It's scoped narrowly by design: if exposed, it can't access your account, existing devices, or the Level API. The only risk is that someone could use it to add devices to your account.
If you believe your install key has been compromised, contact Level support to rotate it.
ℹ️ NOTE: The install key reflects your group selection in real time. Without a group selected, it contains just your account identifier. Select a group and the group's ID is appended.
Install Methods
The modal has two tabs for macOS.
One-Line Command
A curl one-liner that downloads and installs the agent. This is the fastest method and works on any supported architecture without selecting one manually.
In the modal, select the One-line command tab.
Optionally select a device group.
Copy the generated command.
On the target device, open Terminal.
Paste and run the command. You may be prompted for your admin password.
The device shows up in your Device Listing within 5–10 seconds of the install completing.
Installer
Downloads an architecture-specific PKG and installs it manually. Use this when you want a GUI walkthrough or need to specify the architecture explicitly.
In the modal, select the Installer tab.
Select your architecture from the dropdown: x64 (Intel) or ARM64 (Apple Silicon).
Optionally select a device group.
Click Download installer to download the PKG file.
Install using either method:
GUI: Double-click the downloaded PKG and follow the installer wizard.
Terminal: Copy the command shown in the modal and run it in Terminal.
ℹ️ NOTE: The terminal command shown in the modal (sudo installer -pkg ./level-darwin-bundle-amd64.pkg ...) runs the PKG non-interactively and registers the device with your account in one step. The GUI wizard prompts for the install key separately.
🖥️ PLATFORM NOTE:
Intel (x64): Select x64 in the architecture dropdown.
Apple Silicon (M1/M2/M3): Select ARM64. Level uses a service account on Apple Silicon devices to support patch management — you'll be prompted for admin credentials after the install completes. This is expected behavior.
Force Install (Advanced)
If a previous Level install left behind stale files, use the forceInstall URL parameter to force a clean overwrite.
ℹ️ NOTE: forceInstall=true is a URL parameter intended for support scenarios. Level support may link you directly to a pre-configured modal URL when troubleshooting.
Navigate to:
__PRESERVE_CODE_3__
This adds LEVEL_FORCE_INSTALL=true to the generated one-line command.
⚠️ WARNING: Force install overwrites any existing Level agent configuration on the device. Only use this when a standard install fails or Level support directs you to.
Post-Install: Permissions
macOS requires explicit permission grants for remote control, screen recording, and file access. After the agent installs, grant Level access in all three locations under System Settings → Privacy & Security:
Screen Recording
Accessibility
Full Disk Access
You'll need admin credentials to make these changes.
ℹ️ NOTE: The install modal lists these three permissions as a reminder at the bottom of both install tabs.
MDM Deployment: mobileconfig Profile (Optional)
💡 TIP: If you're deploying to many macOS devices, use the mobileconfig profile described below. It silently grants Accessibility and Full Disk Access via MDM, and allows non-admins to approve the Screen Recording prompt without needing admin credentials.
For environments managed by MDM, you can deploy a PPPC (Privacy Preferences Policy Control) mobileconfig profile to streamline the post-install permission setup.
The profile handles Accessibility and Full Disk Access silently via MDM policy. Screen Recording is a protected privacy permission that Apple doesn't allow MDM to grant silently — instead, the profile allows non-admin users to approve the Screen Recording prompt themselves, without needing admin credentials.
⚠️ WARNING: The mobileconfig file provided by Level is a sample only. Level doesn't provide support for creating, managing, or troubleshooting MDM configurations — behavior varies across MDM vendors. Test in your own environment before deploying broadly.
To deploy:
Download the mobileconfig profile: Download Level - PPPC.mobileconfig
Push via your MDM tool, or deploy via script as part of your install process.
Once deployed, Accessibility and Full Disk Access are granted automatically. End users can approve the Screen Recording prompt without admin credentials.
AV/EDR Exclusions
Some antivirus and EDR tools flag Level as a threat. Add Level to your exclusions before deploying to avoid the install being blocked or the agent being quarantined after install.
For exclusion paths, certificate details, and tool-specific instructions, see AV/EDR False Detections. Level also publishes a breakdown of why EDR tools flag RMM agents at level.io/blog/edrs-distrust-rmms-and-thats-ok.
System Requirements
Requirement | Details |
OS | macOS 11 (Big Sur) or later |
Architecture | Intel (x64) and Apple Silicon (ARM64) |
⚠️ WARNING: macOS High Sierra, Mojave, and Catalina will no longer be supported after May 4, 2026.
Storage Locations
Path | Purpose |
| Application binary |
| CLI binary |
| Agent data |
| Launch agent |
| Launch daemon |
After Install
The device appears in your Device Listing within 5–10 seconds and starts populating hardware inventory within a few minutes.
If the device doesn't appear, or goes offline shortly after install, see Offline Troubleshooting.
FAQ
What permissions does Level need on macOS, and why? Level requires Screen Recording (for remote control), Accessibility (for input automation during remote sessions), and Full Disk Access (for file operations and patch management). Without these, remote control and some management features won't work.
Why am I being prompted for admin credentials after the install finishes on my Apple Silicon Mac? Level creates a service account on Apple Silicon devices to support patch management. This prompt is expected — enter admin credentials to complete the setup.
Which architecture should I select in the Installer tab? Select x64 for Intel Macs and ARM64 for Apple Silicon (M1/M2/M3). If you're not sure, check Apple menu → About This Mac. The one-line command method handles architecture detection automatically and doesn't require you to choose.
What's the difference between the GUI installer and the terminal command? Both install the same agent from the same PKG. The GUI wizard prompts for the install key as part of the setup flow. The terminal command (
sudo installer -pkg ...) runs the package non-interactively and passes the install key inline — better for scripted or remote deployments.Can I suppress the permission prompts when deploying to many Macs? Partially. Deploy the Level PPPC mobileconfig profile via MDM — it silently grants Accessibility and Full Disk Access. Screen Recording is a protected Apple privacy permission that MDM can't grant silently, but the profile allows non-admin users to approve that prompt themselves without needing admin credentials.
Can I send end users an email link to install the agent themselves? No. The agent requires local administrator rights, which most end users don't have. Installation needs to be performed by someone with local admin access, manually or via a deployment tool.
What if my install key is compromised? The install key can't access your account, existing devices, or the Level API. The only risk is someone adding devices to your account. Contact Level support to rotate the key if needed.
The device installed but isn't showing up in Level — what's wrong? Wait 10–15 seconds and refresh. If it still doesn't appear, check that all three macOS permissions were granted and that an AV/EDR tool hasn't blocked the agent. See AV/EDR False Detections and Offline Troubleshooting.



