Apps
Add apps from a pre-built catalog by picking the software and version; Pckgr handles packaging and deployment. The Apps page lists the apps available for deployment in your environment.
In short
- Windows and macOS apps are kept apart: use the Windows and macOS tabs at the top of the list to switch between them.
- Adding the latest version turns Auto Update on; adding an older version leaves it off, so the app stays on that version.
- A rollback also turns Auto Update off, so the next catalog release does not move the app forward again.
- Deleting an app also removes its assignments.
Add an app
Go to Software > Apps in the sidebar and click Add App.
Pick the Windows or macOS tab in the catalog dialog.
That platform's packages are listed.Search for the app you want.
Search by name, publisher, or description.Select a package from the list on the left.
Choose a version from the panel on the right.
The latest version is selected by default. Click Show previous versions to see older releases.Click Add App.
The app is added to your environment and ready to be assigned to device groups.
If a version is already in your environment, it shows an Added badge and cannot be selected again.
Auto-update and the version you pick
Not in the catalog? Owners and Admins can click Upload Installer instead and add a Windows app from their own MSI, EXE or ZIP. See Custom Apps.
App templates
The Account Owner, and MSP Technicians granted every tenant, also see two buttons at the top of the page. MSP Read Only users see them greyed out.
- Apply Template
- Add the apps from a saved template to this tenant. Apps that already exist are skipped.
- Save as Template
- Save this tenant’s apps (or the ones you select) as a template to reuse in other tenants.
See Templates for more.
The app list
| Column | What it shows |
|---|---|
| Name | Application name |
| Publisher | Software publisher |
| Version | Package version |
| Intent | Each intent the app is assigned with, such as Install, Available, Update Only or Uninstall; a dash when it is not assigned |
| Assigned to | The groups the app is assigned to, with +N when there are more and how many groups are excluded. Hover to see every group with its intent and exclusions |
| Context | Installation context: System or User |
| Added | Date the app was added to your environment |
Use the search bar to filter by name, publisher, category or assigned group. The assignment filter beside it shows all apps, only apps that are Not assigned, or only apps assigned with one intent. Click the Name or Publisher header to sort.
Select Columns to hide or show Intent and Assigned to. Your choice is remembered in this browser.
App details
Click any app row to open its detail page, which has these panels.
Install and uninstall status
Two cards, Device Install Status and Device Uninstall Status, each show a pie chart of how the app's deployments are going and job counts by status. The counts are each device's latest job for the app; click one to open those devices' deployments on the Deployments page.
Retry N failed queues a new attempt on every device whose latest install (or uninstall) failed, starting again at attempt 1 on a device that has used all its attempts. Devices that already have a newer job are skipped and listed.
Details
Name, publisher, platform, version, install context and when the app was added, plus the Auto Update toggle.
End-user notifications (Windows apps)
Choose whether users see a notification when this app is installed or uninstalled: Inherit (tenant default), On or Off. The tenant default is set in Settings.
Advanced deployment settings
Click Show to open the settings that control how the app is deployed. Changes save as you make them.
- Update DelayImmediate up to 7 days
- How long to wait before deploying a new version from a catalog update.
Windows apps also have:
- Deferral Type
- Silent (No Deferrals), Allow Defer (users can postpone the install), or Allow Defer (If Apps Running) (users can postpone only when an app that must close is open). Any type but Silent shows the user a prompt. While the user's screen is locked, a Windows device holds such an install and starts it once the screen is unlocked. A prompt nobody answers closes after about 55 minutes, and the install is then deferred without using up an attempt.
- Deferral Count1 to 10, 3 by default
- How many times a user can postpone. Each time they do, the install is offered again 12 hours later. A prompt that closes unanswered also counts as a postponement. Once they have used every postponement, the prompt no longer offers Defer and the install goes ahead.
- Apps to Close
- Comma-separated process names (such as
chrome,teams) to close before the install. - Show Progress Dialog
- Show or hide installation progress to the user.
- Restart Prompt
- Prompt the user to restart after installation.
- Remove Desktop Shortcut
- Remove the desktop shortcut the installer creates. Turn it on and enter the shortcut’s file name.
- Custom Install CommandEmpty uses the package defaults
- Replaces the installer's default arguments entirely, including its silent switches, so include the installer's silent switch yourself (for example
/qnor/quietfor MSI installers).
Include a silent switch
Pre and post deployment scripts (Windows apps)
Add PowerShell that runs around the install or uninstall. Save each one with its own button.
- Pre-install script
- Runs first. If it exits with a non-zero code, the deployment stops.
- Post-install script
- Runs after a successful install. Its result is logged but does not fail the deployment.
Assignments
Lists all groups this app is assigned to, with the intent and any excluded groups for each. Click Assign to Group to create a new assignment (see Assignments), click an assignment to change its intent or exclusions, or remove it with the trash icon.

Dependencies
- Install Before This App
- The apps that must install first. Click Add Prerequisite to add one from the apps in your environment, or remove one from the list.
- Required By Other Apps
- The apps that depend on this one.
Update history
Shows previous versions and updates for this app.
Roll an app back
Click Rollback on the app detail page.
The button is shown when older versions are available.Select the target version.
Review the rollback impact preview.
Confirm the rollback.
Pckgr creates new deployment jobs to roll affected devices back to the selected version, and switches the app's detection script to the one that belongs to that version, so the rolled-back install is recognized as installed. On each device the current version is uninstalled first, and the older version installs only after that succeeds; if the uninstall fails, the install is skipped and the device stays on its current version.
The impact preview says where the detection script comes from. Pckgr takes it from the catalog's record of that version, or reads it out of the version's package. When neither has one, the app keeps its current script, the preview says so, and the rolled-back install will report Failed because detection still looks for the newer version. On macOS Pckgr refuses the rollback instead, because the install would succeed and then be reinstalled on every check-in; pick a newer version.
Rollback turns Auto Update off
Delete an app
Click the trash icon on an app row and confirm. If the app has assignments, you'll see a warning showing how many assignments will also be removed.
Bulk operations
Select multiple apps using the checkboxes, then use the action bar. The bar acts only on the apps shown: switching between the Windows and macOS tabs clears the selection, and an app hidden by the search is left out.
- Assign to group
- Assign all selected apps to a group with a specified intent: Install (Required), Uninstall, Update Only, or Available (Self-Service). Available is not offered when a macOS app is selected.
- Save as TemplateAccount Owner and MSP Technicians on every tenant only
- Save the selected apps as a template.
- Delete
- Remove all selected apps. Apps with dependents are skipped.