Triggers for Policies

Triggers are events that initiate a policy. When you create a policy, you can choose one or more pre-defined triggers, or you can choose a custom trigger.

You can use the following pre-defined triggers to run a policy:

• Startup—When a computer starts up. The startup script must be enabled in the Check-In section of Computer Management Settings.

• Login—When a user logs in to a computer. Login hooks must be enabled in the Check-In section of Computer Management Settings.

• Network State Change—When a computer’s network state changes (for example, when the network connection changes, when the computer name changes, or when the IP address changes)

• Enrollment Complete—Immediately after a computer completes the enrollment process

• Recurring Check-In—At the recurring check-in frequency configured in Jamf Pro

  Note:

  On computers with macOS 10.15 or later, Jamf Pro must be safelisted in the Privacy Preferences Policy Control payload to run policies that access data on a network volume at recurring check-in. By default, Jamf Pro is automatically safelisted in the Privacy Preferences Policy Control payload.

• Custom—Initiate the policy manually using the jamf policy -event binary command. For an iBeacon region change event, use beaconStateChange