Skip to main content

App Catalog

Prerequisites

  • Required permissions: Admin or Staff role with access to Fleet > Software Management

  • Supported platforms: Android, iOS, iPadOS, macOS, Windows

  • Time estimate: 15–20 minutes for catalog setup, 3–5 minutes per app addition

  • Additional requirements: MDM activation is required to deploy apps through the App Catalog

Before You Start

The App Catalog is a curated collection of applications available for deployment within your organization. Unlike one-time assignments from app stores, the App Catalog provides admins with a central way to configure patching, deployment behavior, and associations (AutoPilot, device, or group level).

By pre-configuring apps, admins ensure users always have access to approved, secure, and up-to-date software. This prevents shadow IT, enforces compliance, and streamlines app delivery across operating systems.

Step 1: Select Applications for the Catalog

  1. Navigate to Fleet > Software Management > Software Library > App Catalog.

  2. Click + Add New App.

  3. In the App Selection screen, choose applications from the list (Excel, Chrome, Slack, etc.).

  4. Use the search bar or sort by Name to locate apps.

  5. Select the checkboxes for the apps you want to add.

  6. Click Next.

Expected result: The chosen apps are queued for configuration.

Troubleshooting this step:

  • Issue: App missing from list → Solution: Check if it exists in Play Store, App Store, Microsoft Store, or as a custom upload.

Step 2: Configure Application Settings

  1. After selecting apps, proceed to the Configuration screen.

  2. For each app, configure:

    • Auto Updates: Enable/disable automatic patching.

    • Installation Behavior: Choose between:

      • Auto-install (automatically deployed to devices)

      • Self-service (available in company app portal for users to install manually)

    • Command Line Options: (Windows/macOS only) Define install parameters.

  3. Repeat for each selected app (e.g., Chrome, Facebook).

  4. Click Next.

Expected result: Apps are saved with defined patching and deployment rules.

Troubleshooting this step:

  • Issue: Options greyed out → Solution: Ensure you selected from a supported source (App Store, Catalog, or Custom).

Step 3: Associate Applications with Devices and Groups

  1. In the Associations step, choose where to assign apps. Options include:

    • AutoPilot profiles (apps deployed at enrollment)

    • Devices (individual endpoints)

    • Device Groups (collections of endpoints by policy or region)

  2. Select the desired associations.

  3. Click Save.

Expected result: The application is linked to your chosen targets.

Troubleshooting this step:

  • Issue: Device not listed → Solution: Ensure it is enrolled and reporting in Fleet > Devices.

Step 4: Verify Application in Library

  1. Return to Software Library after saving.

  2. The new apps now appear in the list with details:

    • Name & Version

    • Update Status

    • Category

    • Source (Play Store, App Store, Microsoft Store, Custom, Trio Catalog)

    • Assigned Devices/Groups

  3. A confirmation message appears: “Success – New software has been added to the app library.”

Expected result: The applications are successfully cataloged and available for deployment.

Next Steps

Immediate actions:

  • Monitor assigned apps for update compliance.

  • Review associations regularly to ensure apps remain deployed to the right users.

Related configurations:

  • Combine with Software Policy to enforce mandatory apps.

  • Use Event Logs to audit installation attempts and patching history.

Advanced Options

  • Cross-Platform Deployment: Deploy the same app (e.g., Chrome) to Android, iOS, macOS, and Windows.

  • Custom App Distribution: Upload proprietary apps as APK, IPA, PKG, or MSI.

  • Command-Line Deployment: For Windows/macOS, use silent install parameters for advanced control.

Troubleshooting

  • Symptom: App not appearing in catalog → Cause: Unsupported format or missing store entry. → Solution: Verify supported sources and formats.

  • Symptom: Devices not receiving app → Cause: Misconfigured association. → Solution: Recheck AutoPilot, Device, or Group assignment.

  • Symptom: Auto-update not working → Cause: Disabled in configuration. → Solution: Toggle Auto Update in catalog settings.

  • Symptom: Custom upload fails → Cause: Wrong file extension. → Solution: Ensure correct format (APK, IPA, PKG, MSI/EXE).

Did this answer your question?