* Managed feature locks for macOS (#985) * drop unused import * test: string status * Document managed feature locks and loopback-only transforms (#985)
3.4 KiB
Managing Hex in an organization
Administrators can turn Hex features off on managed Macs with a configuration profile. Served at https://anoma.ly/hex/docs/admin.
These keys are macOS only. Windows reads only DisableUpdates (a DWORD
under HKLM or HKCU\SOFTWARE\Policies\Anomaly\Hex), and Linux reads none.
Keys
All keys are Booleans in the anomaly.hex preference domain. A key counts only
when a configuration profile forces it (CFPreferencesAppValueIsForced), so a
value someone writes with defaults write locks nothing. Hex reads them at
launch; a changed profile applies after Hex relaunches.
| Key | Effect |
|---|---|
DisableMeetings |
No meeting detection, recording, transcription, or notes. Meetings recorded before stay readable with hex meetings and hex mcp. |
DisableAnnotate |
Annotate (captures) is off. |
DisableOpenCodeProcessing |
No OpenCode requests: mode rewrites, meeting notes and titles, and sending captures to OpenCode sessions. |
DisableTransforms |
No transforms at all, built in or from hex.config.ts; the config is never loaded. |
RestrictTransformsToLoopback |
Transforms stay on, but fetch reaches only this Mac and node:child_process (exec, execFile) is refused. Every host name, redirects included, must resolve to loopback addresses only (127.0.0.0/8, ::1); the check runs on the resolved addresses Hex connects to, and the system proxy is bypassed. Use it with a local, authenticated model proxy. |
DisableLabs |
Every Labs feature is off. |
DisableUpdates |
Hex never checks for, downloads, or installs updates. |
A locked feature reads as off everywhere: the window shows its setting off
and disabled with "Managed by your organization", and hex settings set,
hex labs on, the local API, shortcuts, and background work all refuse it.
Hex never rewrites the person's own settings, so removing the profile brings
back what they had chosen.
Sample profile
<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE plist PUBLIC "-//Apple//DTD PLIST 1.0//EN" "http://www.apple.com/DTDs/PropertyList-1.0.dtd">
<plist version="1.0">
<dict>
<key>PayloadDisplayName</key>
<string>Hex</string>
<key>PayloadIdentifier</key>
<string>com.example.hex</string>
<key>PayloadType</key>
<string>Configuration</string>
<key>PayloadUUID</key>
<string>9A1C2E3F-0000-4000-8000-000000000001</string>
<key>PayloadVersion</key>
<integer>1</integer>
<key>PayloadContent</key>
<array>
<dict>
<key>PayloadType</key>
<string>anomaly.hex</string>
<key>PayloadIdentifier</key>
<string>com.example.hex.settings</string>
<key>PayloadUUID</key>
<string>9A1C2E3F-0000-4000-8000-000000000002</string>
<key>PayloadVersion</key>
<integer>1</integer>
<key>DisableMeetings</key>
<true/>
<key>DisableOpenCodeProcessing</key>
<true/>
<key>RestrictTransformsToLoopback</key>
<true/>
<key>DisableLabs</key>
<true/>
</dict>
</array>
</dict>
</plist>
Replace the identifiers and UUIDs with your own and leave out the keys you
don't need. Most MDM tools (Jamf, Kandji, Intune, Mosyle) accept the inner
dictionary as a custom settings payload for the anomaly.hex domain.
To check what Hex sees on a Mac: hex labs lists Labs features as managed,
hex settings get meetings.enabled reports it as not writable, and Hex's
process.log names the locks at launch.