Skip to main content

How can I allow or block apps in Jamf School?

This article explains how to configure settings in blueprints and profiles to block or allow apps.

Description

Applications can be hidden or allowed access in Jamf School.

  • A Home Screen Layout can be used to hide or allow apps by reorganizing the user's home screen to only show those certain apps. This will also prevent the user from rearranging their device home screen and removing applications.
    ​

  • If looking for a configuration that doesn't rearrange the user's home screen, then configuring Allow/Deny App Settings via blueprints or Safelist/Blocklist settings in a profile would be more suitable.

    • Allowing/Safelisting Apps: These settings will automatically block apps that are not listed. For example, if Notes is added to the allowed apps list then all other applications on the device will be hidden.

    • Denying/Blocklisting Apps: These settings only hide the specified apps on the device and still allow access to the other apps. For example, if the Mail application is blocklisted it will be hidden on the device but the user still has access to other applications not added to this list.

Keep in Mind:

  • It is not possible to block the "Settings" application.

  • Blocking some applications will inhibit their background functionality. An example would be that blocking the iCloud application will prevent other apps from taking advantage for iCloud for storing resources.


Blocking apps on iOS and macOS 27 using Blueprints

Starting in OS 27, the profile keys to allowlist or blocklist apps through a profile have been deprecated, and declarative management should be used moving forward. This guide will walk through the steps to block apps on iOS and macOS with declarations using Blueprints.

This declaration will use slightly different settings depending on which OS the block should apply to.

Platform

Blueprint component

Setting

Identifier in Blueprint

iOS

App Settings

Denied apps

Bundle Identifier (Bundle ID)

macOS

App Settings

Denied binaries

Code Signing Identifier (Signing ID)

The Code Signing Identifier often matches the Bundle ID for bundle applications, but may differ in rare cases. Always confirm the value shown as Identifier from the codesign output rather than assuming the match.
​
Do not confuse the Code Signing Identity with the Code Signing Identifier. The Code Signing Identity is the certificate used to sign the app.

Blocking an app on iOS

  1. In the configured blueprint, add or open the App Settings component.

  2. Navigate to the Denied apps section.

  3. Enter that bundle ID of each app that should be blocked.

    If the bundle ID of the app to be blocked is unknown, the same steps used to determine App Categories can be used to find this value. Search the downloaded text file for bundleID.

  4. Click Add (or Update).

  5. Set the scope and any activations.

  6. Click Deploy.

Blocking an app on macOS

  1. Open Terminal on a Mac that has the app installed.

  2. Run the following command, replacing AppName with the actual name of the app.

    codesign -v -d "/Applications/AppName.app"
  3. Review the output. The example below uses Google Chrome.

  4. In the configured blueprint, add or open the App Settings component.

  5. Navigate to the Denied binaries section.

  6. Add either of these values to their appropriate section.

    • Signing ID: Blocking binaries by Signing ID will block only processes that have that specific Signing ID predicate.

    • Team ID: Blocking binaries by Team ID will block all applications that are signed by that specific vendor. In the screenshot below, this would block both Google Chrome and Google Drive as they share a Team ID.

  7. Click Add or Update.

  8. Set the scope and any activations.

  9. Click Deploy.

Only allowing specific apps follows the same above steps, though the Allowed apps or Allowed binaries should be used in place of Denied apps or Denied binaries.


Configuring Safelist and Blocklist through a Profile (OS 26 or earlier)

  1. In Jamf School, go to Profiles > Overview and click Create Profile.

  2. Select iOS for the platform, choose Device Enrollment, click Next.

  3. Give the profile a name and a description if desired. Click Next.

  4. Click Finish.

  5. Click the Safelist and Blocklist payload and click Configure.

  6. Select the desired configuration - to safelist or block apps using the dropdown below:

    Image shows the safelist and block applications payload. It shows the Safelist/blocklist applications field where you choose to allow safelisted apps and categories or restrict blocklisted apps and categories..

    • If safelist is selected, this is how the profile looks:

      This image shows the options when allow safelisted apps and categories is selected under safelist/blocklist applications in a jamf school profile.

    • If blocklist is selected, this is how the profile looks like:

      This image shows what options appear when restrict blocklisted apps and categories is selected in safelist/blocklist applications in a Jamf School profile.

  7. Add desired applications to either safelist or blocklist then save the profile using "Add Application".

  8. Scope the profile to desired device groups using the Scope tab.

  9. Click Save.

Did this answer your question?