Pulse on managed Macs
Parable Pulse needs two macOS privacy permissions: Accessibility and Screen Recording. A company’s device management (MDM) tool can install a privacy preferences profile that sets them on each Mac. macOS lets a profile turn on Accessibility. It does not let a profile turn on Screen Recording, so each person still turns that on.What the profile sets
Apple’s payload schema says that a profile can deny screen capture but cannot
grant it. The schema allows
AllowStandardUserToSetSystemService only for
screen capture (ScreenCapture) and input monitoring (ListenEvent).
Until both permissions are on
Pulse collects nothing until both permissions are on. After the person logs in, the Pulse menubar shows Grant Accessibility access… or Grant Screen Recording access… for each permission that is off. The item opens that pane of System Settings. Capture starts when both permissions are on.Requirements
- Install the profile through device management. Apple’s schema accepts it only on the device channel, from an MDM enrollment that the user approved. It does not allow a manual install, so a double-click on the file does not apply it.
- The profile matches only a Parable Pulse build that Parable signs with its
Developer ID, Team ID
ZP6SUBKVZY. It names the app by its bundle identifier,work.parable.pulse.agent, and by its code requirement. - The Pulse background service,
work.parable.pulse.daemon, uses neither permission. The profile has no entry for it.
macOS 27
Apple deprecates the Accessibility setting of this profile in macOS 27. The setting still applies. The Mac also shows a notification for the app, and the person can turn Accessibility off in System Settings. When they do, Pulse stops collecting and the menubar asks for the permission again. Apple names a declarative configuration as the replacement: thePrivacy key
of com.apple.configuration.app.settings. It sets a default that the person
accepts or declines in a prompt. It has no Screen Recording setting. Parable
does not publish that configuration yet.
The profile
Save this text asparable-pulse-privacy.mobileconfig. Upload it to your
device management tool as a custom configuration profile.
parable-pulse-privacy.mobileconfig
Sources
- Apple, Privacy Preferences Policy Control payload schema:
the install channel, the
Authorizationvalues, the screen capture rule, and the macOS 27 deprecation ofAccessibility. - Apple Platform Deployment, Privacy Preferences Policy Control device management payload settings.
- Apple Platform Deployment, Privacy Preferences Policy Control custom payload examples:
Apple’s own screen recording example uses
AllowStandardUserToSetSystemService. - Apple, App settings declarative configuration schema:
the
Privacykey that replaces the Accessibility setting in macOS 27.