> ## Documentation Index
> Fetch the complete documentation index at: https://docs.iru.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Understanding Auto App Settings for macOS

> Configure Auto App settings for macOS in Iru Endpoint. Control version enforcement, phased rollouts, update notifications, Self Service availability, and install behavior.

<Callout icon="apple" color="#B84A7A" iconType="regular">This guide applies to Mac computers</Callout>

Auto App settings for macOS control how the application is installed, how it appears in Self Service, how updates are enforced, and optional install behavior (such as adding the app to the Dock). For Auto App settings on Windows, see [Understanding Auto App Settings for Windows](/en/endpoint/library/auto-apps/understanding-auto-app-settings-for-windows).

### Label

Add a **Label** to distinguish this Library Item from other instances of the same Auto App (e.g., "For Marketing, Notifications Off"). Labels are not displayed to end users; they appear only in the Iru Endpoint Web App. Use labels when you add the same Auto App multiple times with different Blueprint assignments or settings. For steps that apply to any Library Item, see [Library Item Labels](/en/endpoint/library/library-items-profiles/library-overview#library-item-labels) in Library Overview.

### Assignment (Blueprint)

Under **Assignment** → **Assignment Maps**, use **Blueprint** and **+ Assign** to control which devices or users receive this Auto App. Assign the Library Item to the Blueprint(s) that should receive it.

### Installation Method

Under **Installation**, choose how the Auto App is installed:

* **Continuously enforce** — The app is installed and kept up to date automatically on assigned devices.
* **Install on-demand from Self Service** — The app is not pushed; users install it from Self Service when ready.
* **Update only** — Updates are enforced if the app is already installed, but the app is not installed on new computers and is not made available in Self Service.

### Self Service

Under **Self Service**, add this Library Item to Self Service by turning on the **Available in Self Service** toggle. Then configure:

* **Category** — Specify the Self Service category this Library Item displays under. Categories help users find apps in the Self Service library. Recommended items are also displayed in a "Recommended" section at the top of the Self Service library page and categories list.
* **Recommended** — When selected, the item appears in that Recommended section.

Use **Customize** to change the name and content that display in Self Service (see Self Service customization below). Use **Collapse previews** to show or hide the preview cards of how the item will appear.

#### Self Service Customization

Click **Customize** to change the name and content that display in Self Service. The description is shown on the item detail page in Self Service.

<Steps>
  <Step title="Customize name">
    Turn on the toggle to override the default Library Item name displayed in Self Service. Enter a custom name (maximum 30 characters).
  </Step>

  <Step title="Display a description">
    Turn on the toggle to show a description on the item detail page. Choose **Display provided description** (from the Auto App) or **Display custom description** (up to 4,000 characters). A **Copy** button is available to copy the provided description.
  </Step>

  <Step title="Require users to read the description before installing">
    Optionally check **Require users to read the description before installing** so users must view the description before they can install.
  </Step>

  <Step title="Display a link">
    Turn on the toggle to include a support article or documentation link on the item detail page. Set **Text button label** (e.g., "More information"; maximum 32 characters) and **Button URL**. Any URL scheme recognized by the OS can be used, including **https\://**, **mailto://**, and **file://**.
  </Step>
</Steps>

### Manage App Versions

Choose how updates are managed for the Auto App. When enforcement is used, devices always install the latest available version approved by Iru Endpoint.

#### Do Not Manage Updates

Iru Endpoint does not enforce a version of the application. Existing installations are left as-is.

#### Automatically Enforce New Updates

Updates are enforced automatically after release. You set an **Enforcement Timeframe** (how long after release), **Enforcement Time Zone**, and **Enforcement Time**.

<Steps>
  <Step title="Configure Enforcement Timeframe">
    Select the **Enforcement Timeframe** (the amount of time after an update is released before it is automatically enforced).

    **Available options:** 1 day, 2 days, 1 week, 2 weeks, 3 weeks, 1 month, 2 months, 3 months

    Optionally select the **Phased rollout** checkbox under **Enforcement Timeframe**. When selected, choose a rollout window between **1 and 7 days** (in hours). Devices are then offered the update gradually over the rollout period, helping reduce large spikes in download and caching activity, which is especially useful for software titles with large installers.

    When phased rollout is enabled, Iru uses an algorithm that considers the configured rollout window together with device-specific data to determine when each device becomes eligible for the updated version. The timing for each device is shown in the Library Item **Status** tab. For more, see [Library Item Status Activity Timeline](/en/endpoint/library/library-items-profiles/library-item-status-activity-timeline).
  </Step>

  <Step title="Set Enforcement Time Zone">
    Select the **Enforcement Time Zone** to determine when the update is enforced.
  </Step>

  <Step title="Set Enforcement Time">
    Select the **Enforcement Time** (the time of day the update is enforced). Enforcement is determined server-side from the selected **Enforcement Time Zone** (e.g., 5:00 PM PST applies in each device's local time per that zone).
  </Step>

  <Step title="View enforced version information">
    The interface shows the currently enforced version. If you enforce an older version, you may see when newer version(s) will be enforced.
  </Step>
</Steps>

Phased rollout applies to **updates only**. It does not change how initial installs are offered.

If an update must be enforced sooner, [Vulnerability Response](/en/endpoint/vulnerability-management/configure-the-vulnerability-response-library-item) settings take priority over phased rollout.

#### Manually Enforce a Minimum Version

Specify a minimum version (the "floor") and an **Enforcement Deadline**. Useful for critical security updates or aligning devices to a version by a date. Devices below the minimum receive the latest Iru-approved version when they update.

<Steps>
  <Step title="Select Minimum Version">
    Select the **Minimum Version** of the application to enforce. Devices that do not meet this requirement receive the latest available version when they update.
  </Step>

  <Step title="Set Enforcement Deadline">
    Set the **Enforcement Deadline** (the date by which the minimum version must be met).
  </Step>

  <Step title="Set Enforcement Time Zone">
    Select the **Enforcement Time Zone** to determine when the update is enforced.
  </Step>

  <Step title="Set Enforcement Time">
    Select the **Enforcement Time** (the time of day the update is enforced). Enforcement is determined server-side from the selected **Enforcement Time Zone**.
  </Step>
</Steps>

### Auto App Notifications

When notification settings are modified, an updated Configuration Profile is not redistributed until the next daily MDM check-in. To trigger an immediate check-in, run **sudo update-mdm** on the client Mac.

* **Unsupported** — If an Auto App does not post to Notification Center, notifications are not available to customize.
* **Unmanaged** — End users control notification settings. This is the default when an Auto App is added and configured for the first time.
* **Managed** — A Configuration Profile with a notifications payload is installed alongside the Auto App. Use the following steps to configure it:

<Steps>
  <Step title="Enable notification management">
    Turn on the toggle to enforce management of notifications for the Auto App.
  </Step>

  <Step title="Allow or disallow notifications">
    Set whether notifications are **allowed** or **disallowed**. If disallowed, no further options are available and notifications are disabled for the Auto App.
  </Step>

  <Step title="Set notification style">
    Select **None** (available in Notification Center only), **Banner** (default; upper-right corner, auto-dismiss), or **Alert** (stays until dismissed).
  </Step>

  <Step title="Configure critical alerts">
    Optionally enable **critical alerts** so the app can ignore Do Not Disturb and ringer settings.
  </Step>

  <Step title="Configure lock screen and Notification Center">
    Toggle **Show notifications on lock screen** and **Show in Notification Center**.
  </Step>

  <Step title="Configure badge and sounds">
    Toggle **Badge app icon** and **Play sound for notifications**.
  </Step>

  <Step title="Set notification preview visibility">
    Choose **Always**, **When unlocked**, or **Never**.
  </Step>

  <Step title="Set notification grouping">
    Choose **Automatic** (default), **By app**, or **Off**.
  </Step>
</Steps>

If notification settings are updated from **Managed** to **Unmanaged**, when the user is prompted to allow notifications depends on the Auto App (e.g., when the app opens or when it next posts). If an Auto App was configured before this customization existed, edit and save the Library Item so that the granular notification controls apply.

### Options

At the end of the Auto App configuration, the **Options** section includes the following:

* **Add to Dock during install** — When enabled, Iru adds the app icon to the Dock during initial app install, or during re-install if the app is found to be missing. Iru does not automatically re-add the icon to the Dock if the app is updated.
* **Run preinstall script** — The script runs before the app is installed. It must have an exit code of 0 to be considered successful.
* **Run postinstall script** — The script runs after the app is installed. It must have an exit code of 0 to be considered successful.

### Related Articles

<CardGroup cols={2}>
  <Card title="Auto Apps Overview" icon="box" href="/en/endpoint/library/auto-apps/auto-apps-overview">
    Deploy pre-packaged applications across platforms
  </Card>

  <Card title="Understanding Auto App Settings for Windows" icon="microsoft" href="/en/endpoint/library/auto-apps/understanding-auto-app-settings-for-windows">
    Configure installation, Self Service, and update enforcement for Auto Apps on Windows
  </Card>
</CardGroup>