> ## 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.

# Application Blocking User Experience

> See what users experience when application blocking is active on their device. Understand alert dialogs, blocked app behavior, and enforcement messages.

<Callout icon="list-check" color="#B84A7A" iconType="regular">This article covers the user experience on Mac computers, Windows devices, and Android devices</Callout>

This article describes what end users see when an application is blocked by Iru Endpoint on **macOS**, **Windows**, or **Android** devices.

<Warning>
  If you reached this page through a notification, it is because your organization blocked the app you attempted to open. Contact your Iru Endpoint Administrator or IT department for more details. Depending on how the block is configured, the notification window may vary in content.
</Warning>

## Platform-Specific Experiences

<Tabs>
  <Tab title="macOS">
    ### Application Blocking Experience

    <Steps>
      <Step title="User Attempts to Open App">
        A user attempts to open an application that is blocked.
      </Step>

      <Step title="Application Closes">
        The application is immediately closed.
      </Step>

      <Step title="Block Dialog Appears">
        Iru Endpoint displays a block dialog with:

        * The configured **Message**
        * Optionally, a **Button Title** (e.g. *Learn More*)
        * Optionally, the **Button URL**, which opens in the user's default browser if clicked
      </Step>

      <Step title="User Clicks Button">
        If the user clicks the **Learn More** (or equivalent) button, the browser opens to the URL configured in the Library Item.
      </Step>
    </Steps>

    <Note>
      If no button title or URL is configured, the button will not appear in the dialog.
    </Note>

    ### Example Block Dialog

    The macOS block dialog provides clear messaging to users about why an application has been blocked and includes options for additional information if configured by the administrator.
  </Tab>

  <Tab title="Windows">
    ### Application Blocking Experience

    <Steps>
      <Step title="User attempts to launch app">
        A user attempts to launch an application that is blocked.
      </Step>

      <Step title="Application fails to launch">
        The application fails to launch. Windows will enforce the block at the system level.
      </Step>

      <Step title="System message appears">
        A Windows system message will appear indicating that the app is blocked.
      </Step>
    </Steps>

    ### System-Level Enforcement

    Windows enforces application blocking at the operating system level, providing native system messages to inform users that the application cannot be launched.
  </Tab>

  <Tab title="Android">
    ### Application Blocking Experience

    <Steps>
      <Step title="User attempts to access blocked app">
        A user attempts to install or launch a blocked app in the personal profile.
      </Step>

      <Step title="Automatic uninstallation">
        If the app is already installed, Iru Endpoint automatically **uninstalls** it from the personal profile.
      </Step>

      <Step title="Native Android behavior">
        The user will typically see Android's native behavior—such as "App not installed" or missing icon—but no custom Iru Endpoint dialog.
      </Step>
    </Steps>

    <Note>
      On Android, the block experience is silent. No custom modal or message is presented to the user.
    </Note>

    ### Silent Enforcement

    Android application blocking operates silently, removing blocked applications from the personal profile without displaying custom dialogs to users.
  </Tab>
</Tabs>

## Configuration Options

You can configure application blocking through the [**App Blocking** Library Item](/en/endpoint/library/library-items-profiles/configure-the-app-blocking-library-item) with the following options:

* **Blocked Applications**: Specify which applications to block
* **Custom Messages**: Configure user-facing messages (macOS only)
* **Button Configuration**: Add custom buttons with URLs (macOS only)
* **Enforcement Level**: Choose between different blocking methods

## Best Practices

<Steps>
  <Step title="Test blocking policies">
    Before deploying application blocking policies to production devices, test them on designated test devices to ensure they work as expected.
  </Step>

  <Step title="Communicate with users">
    Inform users about application blocking policies through your organization's communication channels to set proper expectations.
  </Step>

  <Step title="Provide alternatives">
    When blocking applications, consider providing approved alternatives or explaining why certain applications are restricted.
  </Step>

  <Step title="Monitor and adjust">
    Regularly review blocked applications and user feedback to ensure policies remain appropriate and effective.
  </Step>
</Steps>