Category filter

Manage app notification settings on macOS devices using configuration profiles

Notifications from different apps on a macOS device can sometimes be overwhelming, leading to distraction and decreased productivity. In this context, using a configuration profile to manage app notifications on macOS devices can be a useful solution. With a configuration profile, you can customize and streamline notification settings for individual or multiple apps, ensuring that the user only receives notifications that are important to them.

Using Hexnode’s Deploy Custom Configuration feature, you can remotely manage app notifications on multiple Macs.

Disclaimer:

The sample configuration profiles provided below are created using various profile creator applications.

Note:

This configuration profile is supported on devices running macOS 10.15 or later.

Manage notification settings of apps

Deploy this configuration profile to disable notifications of the FACETIME app on the devices.

<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE plist PUBLIC "-//Apple//DTD PLIST 1.0//EN" "http://www.apple.com/DTDs/PropertyList-1.0.dtd">
<plist version="1.0">
<dict>
    <key>PayloadContent</key>
    <array>
        <dict>
            <key>NotificationSettings</key>
            <array>
                <dict>
                    <key>AlertType</key>
                    <integer>0</integer>
                    <key>BundleIdentifier</key>
                    <string>com.apple.facetime</string>
                    <key>NotificationsEnabled</key>
                    <false/>
                    <key>ShowInLockScreen</key>
                    <true/>
                    <key>BadgesEnabled</key>
                    <true/>
                    <key>ShowInNotificationCenter</key>
                    <true/>
                    <key>SoundsEnabled</key>
                    <true/>
                    <key>CriticalAlertEnabled</key>
                    <false/>
                </dict>
            </array>
            <key>PayloadIdentifier</key>
            <string>com.apple.notificationsettings.6A689A4C-3156-4F37-8787-4A5828532A13</string>
            <key>PayloadType</key>
            <string>com.apple.notificationsettings</string>
            <key>PayloadUUID</key>
            <string>6A689A4C-3156-4F37-8787-4A5828532A13</string>
            <key>PayloadVersion</key>
            <real>1</real>
        </dict>
    </array>
    <key>PayloadDisplayName</key>
    <string>Notification</string>
    <key>PayloadIdentifier</key>
    <string>macOS.2E066DB1-5663-45EF-BC62-4064805C5FEE</string>
    <key>PayloadType</key>
    <string>Configuration</string>
    <key>PayloadUUID</key>
    <string>2E066DB1-5663-45EF-BC62-4064805C5FEE</string>
    <key>PayloadVersion</key>
    <integer>1</integer>
</dict>
</plist>

<?xml version="1.0" encoding="UTF-8"?>

<!DOCTYPE plist PUBLIC "-//Apple//DTD PLIST 1.0//EN" "http://www.apple.com/DTDs/PropertyList-1.0.dtd">

<dict>

<key>PayloadContent</key>

<array>

<dict>

<key>NotificationSettings</key>

<array>

<dict>

<key>AlertType</key>

<key>BundleIdentifier</key>

<string>com.apple.facetime</string>

<key>NotificationsEnabled</key>

<key>ShowInLockScreen</key>

<true/>

<key>BadgesEnabled</key>

<true/>

<key>ShowInNotificationCenter</key>

<true/>

<key>SoundsEnabled</key>

<true/>

<key>CriticalAlertEnabled</key>

</dict>

</array>

<key>PayloadIdentifier</key>

<string>com.apple.notificationsettings.6A689A4C-3156-4F37-8787-4A5828532A13</string>

<key>PayloadType</key>

<string>com.apple.notificationsettings</string>

<key>PayloadUUID</key>

<key>PayloadVersion</key>

</dict>

</array>

<key>PayloadDisplayName</key>

<string>Notification</string>

<key>PayloadIdentifier</key>

<string>macOS.2E066DB1-5663-45EF-BC62-4064805C5FEE</string>

<key>PayloadType</key>

<string>Configuration</string>

<key>PayloadUUID</key>

<key>PayloadVersion</key>

</dict>

</plist>

Configure the below keys in the configuration profile based on your preferences.

The <key>AlertType</key> key specifies the type of alert for the notifications for the app. It can have the following values:

0: No alert is displayed for the notification.

1: A banner alert is displayed for the notification which disappears automatically after a few seconds.

2: A modal alert is displayed for the notification that requires the user to act before it disappears.

To specify the desired applications, add their bundle identifiers as values for the <key>BundleIdentifier</key> key.
The <key>NotificationsEnabled</key> key is used to enable or disable notifications for the specified app. The configurable values for this key are:

<true/>: Notifications for the app are enabled.

<false/>: Notifications for the app are disabled.

The <key>ShowInLockScreen</key> key configures notifications on the lock screen for this app. The configurable values for this key are:

<true/>: Notifications for the app will be displayed on the lock screen.

<false/>: Notifications for the app will not be displayed on the lock screen.

The <key>BadgesEnabled</key> key is used to enable or disable badges for an app. The configurable values are:

<true/>: Badges for the app are enabled.

<false/>: Badges for the app are disabled.

The <key>ShowInNotificationCenter</key> key configures the notifications in the notification center for this app. The configurable values are:

<true/>: Enables notifications in the notification center for the app.

<false/>: Disables notifications in the notification center for the app.

The <key>SoundsEnabled</key> is used to enable or disable sounds for the app. The configurable values are:

<true/>: Sounds for the app are enabled.

<false/>: Sounds for the app are disabled.

The <key>CriticalAlertEnabled</key> enables or disables critical alerts that can ignore Do Not Disturb and ringer settings for this app. The configurable values are:

<true/>: Critical alerts for the app are enabled.

<false/>: Critical alerts for the app are disabled.

Notes:

To create and customize configuration profiles, you can use tools like Apple Configurator, Profile Manager or manually create them using text editors.
Use non-encrypted .mobileconfig, .xml, or plist files to deploy profiles across devices.
Ensure that you do not associate conflicting configurations with the devices.
Use wildcards to fetch key values from the portal.
It is recommended to manually validate the configuration profile on a system before executing it in bulk.
Hexnode will not be responsible for any damage/loss to the system on the behavior of the configuration profile.

Need more help?

Raise a Ticket

Ask Community

Chat With us