Deploy Screenproof with Kandji
A Custom App Library item for the PKG, and a Custom Profile for the app.screenproof managed preferences. Deploy the PKG first.
1. Deploy the PKG
- Library â add a Custom App (or Auto App if you host the PKG yourself) â upload
Screenproof-<version>.pkg(download the current build fromhttps://updates.screenproof.app/Screenproof-latest.pkg). - Assignment: assign to the Blueprint covering the target Macs.
- Kandji verifies notarization automatically; installs run as
root.
The PKG installs /Applications/Screenproof.app and /Library/LaunchAgents/app.screenproof.agent.plist (per-user agent, RunAtLoad â starts at each user's next login, not at boot). The installer is signed Developer ID Installer, team S65X5KY399, and notarized.
2. Deploy the managed-preferences profile
- Build your profile: start from
examples/managed-preferences.mobileconfigor the Profile Creator. - Library â Custom Profile â upload the
.mobileconfig. Kandji passesmcx_preference_settingspayloads through unmodified. - Assign to the same Blueprint.
Deploy the optional restrictions profile as another Custom Profile. For the PPPC denylist, Kandji also has a native editor: Library â Privacy Preferences Policy Control.
3. Verify on a target Mac
- Open Screenproof â Settings â Managed: the managed banner appears with your org's enforced values.
- In the Privacy / Export / License tabs, rows forced by the profile show lock icons and read "Managed by your organization".
- Open Policy Diagnostics: each forced key lists a MANAGED source.
sudo /usr/libexec/mdmclient QueryInstalledProfiles # profile present
defaults read /Library/Managed\ Preferences/app.screenproof
Live-reload under Kandji push: not yet re-validated Screenproof reads managed keys at policy-resolution time â no daemon restart required in principle â but live-reload behavior under Kandji push updates has not been re-validated. Confirm in your trial deploy: push the profile, change one key, re-push, and check Policy Diagnostics picks up the new value without a relaunch.
Next steps
- Screen Recording permission â the one-time user approval MDM cannot skip, plus native-capture lockdown.
- Fleet licensing â add
LicenseKeyto the same profile. - Updates â silent Sparkle updates via three more keys.