Edit the Managed Preferences that the Jamf Pro Blueprint interface can't.
Archived in November 2026. Blueprint Managed Preferences Editor is no longer
maintained. Blueshift by Jamf Concepts now edits the Managed Preferences
values that the Jamf Pro Blueprint editor can't open, on any Blueprint, as a form or a plist.
Deploying is done in Jamf Pro. The app's last release, its source and its documentation stay
on GitHub.
When Jamf Pro turns a classic configuration profile with an Application & Custom Settings
payload into a Blueprint, that payload becomes a legacy Managed Preferences payload
(com.apple.ManagedClient.preferences). The Jamf Pro interface shows it but can't
edit it, and points to the Jamf Platform API instead. Blueprint Managed Preferences Editor is
a macOS app that uses that API for you: it finds every Blueprint with a Managed Preferences
payload, lets you edit the payload in an outline editor, and saves your changes back without
touching anything else in the Blueprint. Deploying stays a separate, explicit step.
Free and open source. Blueprint Managed Preferences Editor is released under
the MIT license. Downloads, documentation and the full source are on
GitHub.
Sample Blueprints in Demo Mode, with one preference domain open in the outline editorThe review before saving: every changed key with its old and new value
What it does
Discovery — every Blueprint that contains Managed Preferences, with its
deployment state, last update and preference domains. Search by name, description or
domain, switch to All Blueprints to see the rest, or use Fetch by ID to load one
Blueprint you know.
Domains — add, rename and remove preference domains, and switch each one
between Forced, Set-Once and Often.
Outline editor — in the style of Xcode's property list editor, with
String, Integer, Real, Boolean, Date, Data, Array and Dictionary types. Add, delete,
duplicate, reorder and nest items; values are validated as you edit.
Import and export — import domains, or replace one domain's settings,
from a .plist, a .mobileconfig (signed or unsigned) or pasted
text, and export any domain as a .plist.
Review before saving — a diff of old and new values for each domain and
key, then Save or Save & Deploy.
Undo and redo for every edit. Unsaved changes are marked on the window
and in the sidebar, and Discard Changes, Reload from Server and Quit ask before they're
lost.
Multiple connections to switch between tenants. While a save, deploy or
restore runs, switching waits until it has finished, so its backup and result stay with
the connection in use.
Blueprint menu — Save (⌘S), Save & Deploy (⌥⌘S), Deploy (⇧⌘D),
Restore from Backup and the domain commands, also from the keyboard. Results such as
Saved and Deployment Started appear in the window.
Blueprint JSON — the Blueprint as received, and with unsaved edits the exact
request body Save will send, each with Copy and Save.
Saving safely
The Jamf Platform API applies Blueprint updates as a JSON merge-patch, and a merge-patch
replaces arrays wholesale, so a careless save can delete parts of a Blueprint. The app guards
against that:
Nothing outside your edit changes. Every save sends the complete
steps array, with every step and component exactly as it was received except
the Managed Preferences you edited.
Concurrent changes are caught. Just before saving, restoring or
deploying, the Blueprint is fetched again. Save and Restore, which send only the steps,
stop when the steps changed on the server; Deploy also stops when the scope changed, so
a deployment never goes to a scope you didn't confirm. The message says what
changed.
Every save and restore is backed up first. The full Blueprint is written
to your Library, and Restore from Backup puts those steps back.
Division-locked Blueprints are left alone.divisionId is
never sent, and Blueprints Jamf assigns to a division are read-only.
Deployment needs confirmation. After a save the Blueprint shows
Out of Date until you deploy it, and deploying asks for confirmation with the
Blueprint's name and scope. Deploy is unavailable while edits are unsaved; Save &
Deploy in the review does both.
When Jamf asks the app to wait before trying again, at most 60 seconds, the wait is shown
with Stop, which ends only the waits shown beside it. After Stop, the message says whether
anything may have reached Jamf; nothing is sent again.
The app sends only GET requests, token requests, and Blueprint update and deploy requests.
Trying it without a tenant
Click Try Demo Mode in the main window, or choose Demo Mode in the connection picker or the
Connection menu. Sample Contoso Blueprints with Managed Preferences — Microsoft AutoUpdate,
Outlook, Chrome with nested settings and a list, and a helpdesk app — can be edited, saved,
deployed and restored inside the app. The picker reads “Contoso (Demo)”, window titles end in
“— Demo”, nothing is sent to a tenant, and everything resets when the app quits.
Privacy and security
Blueprint Managed Preferences Editor has no account system, no analytics and no advertising.
It talks only to the Jamf Platform API in your region and, once a day, to GitHub to ask
whether a newer release exists (turn that off in Settings › Updates). Client secrets are
stored in the Keychain. The Activity Log (Window › Activity Log, ⇧⌘L) is kept in memory with
tokens and secrets redacted; request contents are never recorded, and Export for Bug Report
replaces device identifiers, usernames, email and IP addresses with placeholders. The
developer operates no servers and receives no data.
Backups hold the full Blueprint as it was on the server, including any values in its Managed
Preferences such as license keys, but no Jamf credentials. They're stored unencrypted in your
user Library, one per save and restore, and the app never deletes them: Show Backups in
Finder takes you there.
Known limitations
JSON has no Date or Data type, so those values are sent as ISO 8601 and Base64 strings,
and load back as String.
Scope is shown as device group IDs: the app doesn't read device groups, so it needs no
device-groups permission.
Payloads or domains with an unexpected shape are shown read-only and saved back
unchanged.
Moving to Blueshift
Blueshift, a Jamf Concepts app for moving classic configuration profiles
to Blueprints, edits the Managed Preferences values that the Jamf Pro Blueprint editor
can't open, on any Blueprint. Its Edit Values shows each preference domain as a form or as
a plist, imports a .plist or .mobileconfig (replacing or merging),
and lists every change before it saves. Blueshift never deploys a Blueprint: deploy it in
Jamf Pro after saving.
Requirements
macOS 15 or later.
A Jamf Platform API client (US, EU or APAC region) with blueprints:read,
blueprints:update and blueprints:deploy. Test Connection checks
only reading; the write permissions can't be checked without writing.
The Environment ID, which Load Environments in Settings › Connections fills in for an
organization-scoped client, or copied from the integration in
Jamf Account. It's a UUID; the connection editor
says so when it isn't.
Getting it
Download the latest signed and notarized build from the
releases page,
or build it yourself from source — it needs Xcode 27 or later, and its only dependency,
JTKit, is resolved from GitHub. Bug reports and feature requests are welcome as
GitHub issues.
The app offers new releases itself: a daily check, or on demand from the app menu, with
release notes and a download. It can be turned off in Settings › Updates.