Deploy with Jamf Pro

Install and enroll Tokenize on Jamf Pro-managed Macs with one policy and the Jamf enrollment script.

If you manage Macs with Jamf Pro, use the Jamf script from the dashboard. Jamf runs it from the same policy that installs the package, so nobody runs anything by hand on the Mac. Jamf Pro is Mac only. For Windows PCs, see Deploy with MDM.

Who can do this: Admins create the enrollment key. A Jamf Pro admin uploads the package and script and creates the policy.

Step 1: Create an enrollment key

  1. Go to Settings → Downloads and click Deploy with MDM.
  2. Check the allowed email domains. Click Add another domain if you need more.
  3. Click Create key and copy it. It's shown once and expires after 90 days.

See Deploy with MDM for how domains limit who can enroll.

Step 2: Download the files

Under Deploy, choose Jamf for How does IT deploy?. Download both:

  • Download Mac installer
  • Download Mac script

Once you've created a key on this page, the script you download already has the key written into it. The page then reads "No parameters needed. The enrollment key is already in the script." The downloaded script contains the key, so treat the file like a password, and revoke the key after rollout.

If the dashboard shows "Couldn't add the enrollment key to the script", download the plain script and set Parameter 4 in the policy to the enrollment key the page shows.

Step 3: Create the policy

  1. Upload the package and the script to Jamf Pro. Don't edit the script.
  2. Create a policy with both. Set the script to run After, so the package installs first.
  3. Trigger it on Enrollment Complete or Recurring Check-in, with Execution Frequency Once per computer.
  4. Turn on Automatically re-run policy on failure, so Macs with no one logged in retry later.
  5. Scope it to a few pilot Macs first, then widen it.

The script needs someone logged in to know whose Mac it is. It uses the email the person is signed in with in Claude Code, Cursor, or Codex, and the Mac's serial number as its device ID. If it runs on a Mac that's already enrolled, it exits without enrolling again.

Macs with no Claude Code, Cursor, or Codex login

The script can also read each person's email from a Jamf configuration profile:

  1. In Jamf Pro, check that each computer has the person's work email under Inventory → User and Location → Email Address.
  2. Create a computer-level configuration profile with an Application & Custom Settings payload. Use the preference domain dev.palindromelabs.transcript-shipper.enrollment and this property list:
<?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>Email</key>
	<string>$EMAIL</string>
</dict>
</plist>
  1. Scope it to the same Macs as the policy.

Type $EMAIL exactly as shown. Jamf replaces it with each computer's email. The palindromelabs name in the domain is expected.

Don't put OrgId or APIKey in this profile or any other Tokenize profile. The script creates a key for each Mac, and managed values would override it.

Check that it worked

In the policy log for a pilot Mac, a run that worked ends with a line like:

==> SUCCESS: enrolled device "Paul's MacBook" (C02…) in Tokenize prod as paul@example.com for paul.

Admins can then see the Mac's key under Settings → API keys, with the person in the Owner column. See Manage your devices.

If a run fails

Lines starting with ERROR: in the policy log say why. The script never prints the enrollment key.

CodeMeaningWhat to do
0Enrolled, or already enrolledNothing
1The server refused every email it tried, or another failure"device is not eligible for enrollment" means the email isn't on an allowed domain. Fix the email, or create a key that allows that domain.
2Enrollment key rejectedThe key is wrong, expired, or revoked. Create a new one.
3Network, rate-limit, or server errorLet the retry run it again
10App signature invalidUpload the package from the dashboard again
11No logged-in user, or no email foundNobody logged in is expected; it retries. No email: see the section above.
12No enrollment key, a bad parameter, or not run as root"this copy of the script has no enrollment key" means you need the key in the script or in Parameter 4
13App not installedSet the script to run After in the same policy as the package
14Enrolled, but the status check failedContact your Tokenize account team with the policy log