AppTidy
Jamf Pro

Deploy AppTidy with Jamf Self Service.

Publish AppTidy to managed Macs with a Jamf Pro policy. Use Self Service or Self Service+ for user-initiated install, or scope a required policy after pilot testing.

Last updated: June 20, 2026

Enterprise overview Intune guide

A signed PKG is usually the cleanest enterprise package for Jamf policy deployment. If your current release is a signed and notarized DMG, document that as the current path and add a PKG workflow when available. Jamf's current docs distinguish Self Service classic from Self Service+; use whichever end-user app your organization has standardized on.

App Details

Bundle ID com.apptidy.AppTidy
Install path /Applications/AppTidy.app
Minimum OS macOS 13 or later
Recommended package Signed and notarized PKG for Jamf policies when available; signed DMG as the current direct-download path.

Step-by-Step Deployment

Download the final package

Use the production signed and notarized AppTidy release. Prefer a PKG for Jamf policy deployment when available; otherwise use the approved DMG package workflow.

Upload to Jamf Pro

In Jamf Pro, upload the package or DMG to your distribution point or Jamf Cloud distribution point.

Create a policy

Create a new policy for AppTidy. Configure the trigger and execution frequency based on whether the install is required or user-initiated.

Add the package

Add the AppTidy package to the policy Packages payload. Confirm the package installs AppTidy to /Applications/AppTidy.app.

Scope the policy

Scope the policy to a pilot smart group first, then broaden to target departments, device groups, or all managed Macs after validation.

Add Self Service details

For user-initiated install, enable the policy in Self Service or Self Service+, add the AppTidy icon, and use a concise description that explains review-first cleanup.

Test on a clean Mac

Run the policy on a test Mac, confirm AppTidy launches, and verify the installed app bundle ID is com.apptidy.AppTidy.

Optional PPPC Profile

Use a Jamf computer configuration profile if the organization wants to manage privacy permissions such as Full Disk Access. Use identifier com.apptidy.AppTidy, identifier type bundleID, and the final Developer ID-signed code requirement. Full Disk Access helps scan protected user data, but it does not bypass administrator approval for root-owned app bundles.

Troubleshooting

  • If the policy runs but AppTidy is missing, confirm the package payload installs into /Applications.
  • If Self Service install is unavailable, check policy scope, category, and Self Service settings.
  • If privacy permissions do not apply, rebuild the PPPC profile using the final signed AppTidy code requirement and redeploy the configuration profile.
  • If macOS requests administrator approval during app removal, that approval is expected for root-owned app bundles and is separate from Full Disk Access.

Official References