Skip to main content
A managed device policy is a setting you push to company computers so that people can’t change it themselves. With one, you can:
  • keep OpenWhispr local-only: speech-to-text and AI run on the computer itself, with no sign-in and no cloud
  • require sign-in, so the app applies your OpenWhispr workspace’s rules
  • turn off meeting recording
  • deploy a full policy that sets every control in one value
The device policy is free. It needs no OpenWhispr account, plan, or workspace. That includes the local-only lock.
Device policies need OpenWhispr 1.12.0 or newer. Older versions ignore them, so deploy 1.12.0 or newer before you deploy the policy.

Where OpenWhispr reads the policy

Each operating system has its own place for it. The app reads only these places, so a person without admin rights can’t create or change a policy. On macOS, OpenWhispr reads only values that a configuration profile enforces. A value set with defaults write doesn’t count. You can push the profile to the computer or to a user.

The settings

Set only the ones you need. A setting you leave out is not enforced.

RequireSignIn set to false: local-only

This is the lock most IT teams ask for. With it:
  • speech-to-text and AI features can use only models that run on the computer
  • people can’t add their own cloud API keys or choose a cloud provider
  • the app skips sign-in during setup, and sign-in is turned off on that computer
  • web search, connectors, cloud backup, and share links are off
  • the app blocks its own connections to OpenWhispr’s servers and to every cloud AI provider
Two downloads still work: models, when someone picks a local model, and app updates. See Local model downloads for the hosts they use. To stop the app updating itself as well, deploy a full policy with "updates": { "mode": "it_managed" }. If someone was signed in before you deployed the lock, they stay signed in, but the app makes no cloud requests for that account. The app tells them: This device uses local processing only. Cloud features are unavailable, including for previously signed-in accounts.

RequireSignIn set to true: sign-in required

People must sign in before they can use OpenWhispr. After they sign in, the app combines your device policy with their workspace’s policy, and the stricter of the two wins for each control. Use this with single sign-on to make sure every company computer follows your workspace’s rules.

DisableMeetingRecording set to true

This turns off meeting recording and leaves the rest of the app alone. You can combine it with either value of RequireSignIn.

Deploy on macOS with Jamf Pro

You can paste the setting into Jamf Pro, or upload a ready-made profile. Both give the same result.

Option A: paste the setting

1

Create the profile

In Jamf Pro, go to Computers → Configuration Profiles → New. Give it a name, such as OpenWhispr: local processing only, and set Level to Computer Level.
2

Add the preference domain

Open the Application & Custom Settings payload and choose Upload. Select Add, then enter com.gizmolabs.openwhispr as the Preference Domain.
3

Paste the setting

Paste this into Property List:
4

Scope and save

On the Scope tab, add the computers or groups, then select Save.

Option B: upload the sample profile

Save this as openwhispr-local-only.mobileconfig. In Jamf Pro, go to Computers → Configuration Profiles → Upload, choose the file, set the scope, and save.
openwhispr-local-only.mobileconfig
You can change PayloadOrganization to your company name. To turn off meeting recording as well, add these two lines under RequireSignIn in the inner mcx_preference_settings block:
Write true and false as <true/> and <false/>. A number such as <integer>0</integer> or the text <string>false</string> makes the policy invalid, and OpenWhispr stops working on that computer until it’s fixed.

Check it on a Mac

After the profile installs, open System Settings → General → Device Management (older macOS: Privacy & Security → Profiles). The OpenWhispr profile should be listed. In Terminal, this should print RequireSignIn = 0;:
A profile pushed to a user rather than the computer is in /Library/Managed Preferences/<username>/ instead. Then open OpenWhispr. Setup skips sign-in, and only on-device models are offered.

Deploy on Windows

Create the values under HKLM\SOFTWARE\Policies\OpenWhispr: For example, from an elevated Command Prompt:
Use the 64-bit registry. A value a 32-bit tool writes under WOW6432Node is not read. On/off values must be REG_DWORD set to 0 or 1. Any other type or number makes the policy invalid.

Deploy on Linux

OpenWhispr reads two files from /etc/openwhispr:
  • device.json holds RequireSignIn and DisableMeetingRecording
  • policy.json holds a full policy, written as a plain JSON object, not as text
For local-only:
To keep anyone else from planting a policy, OpenWhispr trusts the folder and files only when all of these are true:
  • the folder and both files are owned by root, and only root can write to them
  • /etc is owned by root, and only root can write to it
  • neither the folder nor the files are symbolic links
  • each file is 1 MB or smaller
If a file breaks one of these rules, OpenWhispr treats the policy as invalid. Don’t put a Policy key in device.json: put the policy in policy.json.

Full policy

The Policy setting holds every control in one JSON value. It uses the same format as an OpenWhispr workspace policy. Use it when the three simple settings aren’t enough, for example to allow only certain cloud providers or to manage updates yourself. This example keeps the app local-only, turns off meeting recording, and stops the app updating itself:
requiredLocalModels, updates, transcription.allowedEnterpriseProviders, and every feature except agentEnabled and webSearchEnabled can be left out. A feature you leave out stays on. Every other field is required: a policy with a missing required field, or a value the app doesn’t recognise, is invalid. How to deploy it:
  • macOS: add a Policy key whose value is a <string> holding the JSON. Escape <, > and & if your JSON contains them.
  • Windows: a REG_SZ value named Policy holding the JSON.
  • Linux: the JSON object itself, as /etc/openwhispr/policy.json.
If you deploy Policy without RequireSignIn, OpenWhispr requires sign-in. To use a full policy on computers where nobody signs in, also set RequireSignIn to false.

When changes take effect

OpenWhispr checks for a new or changed policy every minute while it runs, and again when someone switches back to the app. On macOS and Linux, it also notices a change to the policy files within seconds. No restart is needed. To remove the policy, remove the profile, registry key or files. OpenWhispr goes back to normal at its next check.

If the policy is invalid

If OpenWhispr finds a policy it can’t use, it doesn’t fall back to no policy. It stops working on that computer and shows: The device policy could not be read or is invalid. Contact your administrator. Fix or remove the policy and the app recovers within a minute. Common causes: