How-To: Create Smart Software Items (.pkg files) – Addigy

This guide walks you through creating a Smart Software item using a .pkg installer file. Whether you're new to Addigy or just getting started with MDM, follow the steps below to get your software packaged and ready to deploy.

Note: For a general overview of Smart Software and its deployment options, see Smart Software Overview before proceeding.

Before You Begin

Before creating a Smart Software item from scratch, check the Prebuilt Apps Catalog to see if a ready-to-use installer already exists for the application you need. If it's available there, you can skip this process entirely.

If the app isn't in the Prebuilt Apps Catalog, continue with the steps below.

How to Create a Smart Software Item (.pkg)

Navigate to Catalog > Software > Smart Software and click New.
Enter a name for your Smart Software item and specify a Version.

Note: The software name cannot be changed after creation.
Under the Installation section, click Select File(s) to open the File Manager.
Upload your .pkg file, then select it to attach it to the Smart Software item.
Once the file is attached, click Add under the Install Command column. Addigy will auto-fill the installation command based on the uploaded file.

Tip: The auto-filled command uses /usr/sbin/installer to install the .pkg file and targets the boot volume by default. Verify the command looks correct before saving.
Review the auto-filled Installation Command to confirm it is accurate.
Optionally, add a Condition for Install (see below).
Click Save to create the Smart Software item.

Your new Smart Software item is now ready to be added to a policy or Self Service configuration for deployment.

Condition for Install (Optional)

A Condition for Install is a check that runs on the device before the installation command is executed. It's optional, but highly recommended — it allows Addigy to verify whether the software needs to be installed or reinstalled, rather than running the installer unconditionally.

Common conditions include:

If app — Check whether a specific application is present, and optionally check its version
If OS version — Only install on devices running a specific macOS version
If device architecture — Target Intel or Apple Silicon devices specifically
If file exists / does not exist — Check for the presence of a specific file path
If profile exists — Check whether a specific MDM profile is installed
If process not running — Only install when a specific process is not active

Note: If no Condition for Install is set, the installation will only be attempted once after the item is added to a policy. Adding a condition enables reinstallation to be reattempted on future policy runs whenever the condition is met. For more detail, see Condition for Install Explained.

Next Steps

Once your Smart Software item is saved, you can deploy it in the following ways:

Deploy via Policy — add the item to a Parent or Child policy to deploy it automatically to all devices in that policy. See Adding Items to a Policy for details.
Deploy via Self Service — make the item available for end users to install on demand from the Self Service app. See Adding or Removing Software in the Self Service Catalog.
Deploy to an Individual Device — use GoLive to deploy the item to a single device on demand. See Deploying Software to Individual Devices in GoLive for details.

Frequently Asked Questions

Can I change the software name after saving?

No. The software name is locked after the item is created. Choose your name carefully before saving — if you need to rename it, you'll need to create a new Smart Software item.

What does the auto-filled installation command do?

Addigy generates a standard /usr/sbin/installer command that installs the .pkg file to the root volume (-target /). For most standard .pkg installers this works without modification, but always verify the command matches any requirements in the developer's documentation.

Where is the .pkg file stored after upload?

Uploaded files are stored in Addigy's File Manager and downloaded to the device at /Library/Addigy/ansible/packages/[Software Name (Version)]/ before the installation command runs.

What if the installation requires additional MDM permissions?

Some applications require MDM profiles (Device Settings in Addigy) to be deployed alongside the installer for a silent installation — for example, Full Disk Access or System Extension approvals. Consult the software developer's MDM documentation to determine if any accompanying profiles are needed, and configure them in Catalog > Device Settings.