Deploy Wispr Flow via MDM

Last updated: September 19, 2026

Available on: Mac and Windows, with an Enterprise subscription and MDM-managed devices.

Deploy the installer, required Mac permission and ownership files, and an optional update policy. Then verify the rollout on a test device.

Before you deploy

  • Mac: macOS 12.0 or later. Use the Apple Silicon .pkg for M-series Macs and the Intel .pkg for Intel Macs; Intel builds cannot run under Rosetta 2.

  • Windows: x64 architecture is required; ARM devices are unsupported. Use the machine-wide MDM Wispr Flow.msi, not a per-user installer.

Sign in to admin.wisprflow.ai as an Admin, SuperAdmin, or IT Admin. Open the MDM section and use Copy link for download URLs. Configuration profiles, PowerShell scripts, and ownership scripts arrive as ZIP files: unzip them before deployment.

Permissions and security: Only macOS Accessibility can be pre-granted through MDM. Users must approve Microphone access themselves on first use; Automation permission is not required. The Mac app and PKG are signed and notarized. Do not disable Gatekeeper. These profiles are for managed devices only.

If your organization restricts outbound traffic or uses an IP allowlist, review Configure your network for Wispr Flow before rollout.

Deploy on macOS

  1. Upload the architecture-specific .pkg to your MDM and target your devices. It installs silently to /Applications.

  2. Deploy the unzipped Accessibility .mobileconfig to the device, not just the user. Deploy it before or alongside the app. The signed profile remains valid across app updates and does not need redeployment for each release.

  3. Deploy the unzipped Restore App Ownership script from the portal. The app bundle must be writable by the current user for self-updates; this script prevents admin-password prompts after MDM installation. If prompts persist, follow the admin-password troubleshooting guide.

Download and unzip the ownership script instead of pasting its contents from a browser, which can introduce line-ending errors. If a PKG updates a running app, have users quit and relaunch to run the new version.

The app must run from /Applications, ~/Applications, or /System/Applications. For permission profiles, use bundle ID com.electron.wispr-flow, Team ID C9VQZ78H85, developer Wispr AI INC, and this code requirement:

identifier "com.electron.wispr-flow" and anchor apple generic and certificate 1[field.1.2.840.113635.100.6.2.6] and certificate leaf[field.1.2.840.113635.100.6.1.13] and certificate leaf[subject.OU] = C9VQZ78H85

Deploy on Windows

Upload the machine-wide MSI as a line-of-business app and deploy as SYSTEM, not in user context. Run:

msiexec /i "Wispr Flow.msi" /quiet

Confirm %ProgramFiles%\Wispr Flow\ exists, then launch Flow. This install location cannot be customized; application data is stored at %APPDATA%\Wispr Flow\. Accessibility is not required. In Windows microphone settings, enable both Microphone access and Let desktop apps access your microphone. Publisher matching should accept Wispr AI INC or Wispr AI.

The MSI upgrade identifier stays the same across releases, allowing your MDM to recognize new packages as upgrades.

To silently remove an MSI deployment, run msiexec /x "Wispr Flow-v<version>.msi" /quiet with the matching installer package.

Find the deployment controls in your MDM

Provider

Installer, profile, and script locations

Jamf Pro

Settings → Packages; target computers in a deployment policy. Upload the Accessibility profile under Configuration Profiles → Upload and add the ownership script to the policy.

Kandji

Library → Custom Apps → Add Custom App for the PKG; Library → Custom Profiles → Add Profile for Accessibility. See the ownership warning below.

Intune

Apps → macOS → Add → Line-of-business app, or Apps → Windows → Add → Line-of-business app. Mac profiles: Devices → Configuration profiles → Create profile → Templates → Custom; ownership: Devices → Scripts.

Rippling

IT → Device Management → Software, with silent installation. Mac profiles: IT → Device Management → Configuration Profiles. Add ownership and Windows update-policy scripts as post-install scripts.

Mosyle

Management → Apps → Custom Apps; Accessibility under Management → Profiles → Custom Profiles; ownership under Management → Scripts.

Munki

Run munkiimport "Wispr Flow.pkg". Set installer_type appropriately and an installcheck_script checking /Applications/Wispr Flow.app and its version. Deploy Accessibility separately through MDM; Munki does not manage profiles.

Fleet

Add the PKG to the software library or a custom policy. Use Fleet MDM profile management for Accessibility. Verify with SELECT * FROM apps WHERE name = 'Wispr Flow'.

Kandji: Use Auto App → Postinstall for Restore App Ownership. With Custom Script → Audit & Enforce, a non-zero exit can reinstall the app and undo ownership changes. The supplied script always exits 0.

Choose an update policy

Automatic updates are enabled by default. If your organization needs a managed schedule, follow Configure auto-update policy via MDM. That guide covers the supported schedules, Mac profile, Windows registry and PowerShell options, and verification.

Verify the rollout

Launch Flow on a test Mac. Accessibility should show a green checkmark; approve the one-time Microphone prompt. If Accessibility is missing, check System Settings → Profiles and device-level deployment. On macOS 15+, a restart may be needed. Users complete onboarding privacy choices unless organization policy locks them.

Check the Mac version with:

defaults read /Applications/Wispr\ Flow.app/Contents/Info.plist CFBundleShortVersionString

On Windows, find the Wispr Flow entry under HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall.

For other MDMs, use one that supports custom .mobileconfig profiles or contact support. Contact support for deployment or network problems; include your MDM provider, OS version, Flow version, and steps tried.