> ## 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 Windows > Configure Auto App settings for Windows in Iru Endpoint. Control installation behavior, Self Service availability, and update enforcement policies. This guide applies to Windows devices Auto App settings for Windows control how the application is installed, how it appears in Self Service, and how application updates are enforced. For macOS-specific settings, see [Understanding Auto App Settings for macOS](/en/endpoint/library/auto-apps/understanding-auto-app-settings-for-macos). For what end users see when **Auto App** or **Windows Custom App** installs or updates on Windows wait on running apps, see [User Experience with Windows Apps](/en/endpoint/library/library-items-profiles/user-experience-with-windows-apps). ### Label Add a **Label** to distinguish this Library Item from other instances of the same Auto App (e.g., "For Marketing"). 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. ### Blueprint Assignment Use **Blueprints** 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 **Settings**, choose how the Auto App is installed: * **Install and 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. An **Available in Self Service** toggle controls whether the item appears in the Self Service catalog when the installation method allows it. ### Self Service When the Auto App can be offered in Self Service, you can configure: * **Available in Self Service** — Toggle visibility in the Self Service catalog. * **Category** — Self Service category this Library Item displays under. Categories help users find apps in the Self Service library. * **Recommended** — When selected, the item also appears in a "Recommended" section at the top of the Self Service library and in the categories list. #### Self Service Customization Click **Customize** to open the Self Service customization options. The description is displayed on the item detail page in Self Service. * **Customize name** — Override the default Library Item name displayed in Self Service (toggle on to enable). * **Display a description** — 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. * **Display a link** — Add a support article, documentation, setup instructions, or support portal link on the item detail page in Self Service. When enabled, set: * **Text button label** — Label for the button (e.g., "More information"). Maximum 32 characters. * **Button URL** — Any URL scheme recognized by the OS can be used, including **https\://**, **mailto://**, and **file://**. ### Enforcement (Update Management) Under **Enforcement**, choose whether updates are not managed, are automatically enforced after release, or a minimum application version is enforced. When enforcement is used, the latest update of the Auto App is always installed on devices below the required version. Updates are cached on devices and users can voluntarily update before the enforcement deadline. **Windows Auto App updates are always enforced in the device’s local time zone.** The time you set is applied in each device’s local time, not server time. #### Do Not Manage Updates Iru Endpoint does not enforce a specific version of the application. Existing installations are left as-is. #### Automatically Enforce New Updates Updates are enforced automatically after release. Configure the **Enforcement Timeframe** (how long after release) and **Enforcement Time** (time of day). Enforcement occurs at that time in each device’s local time zone. The interface shows the currently enforced (minimum allowed) version. 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 Select the **Enforcement Time** (e.g., 12:00 PM). Enforcement occurs at this time in each device's local time zone. The interface shows the currently enforced version (e.g., "App 25.1.20937.0 is currently the minimum allowed version"). If you enforce an older version, you may see when newer version(s) will be enforced. #### Manually Enforce a Minimum Version Specify a minimum version (the "floor") and an enforcement deadline (date and time). Useful for critical security updates or aligning all devices to a version by a date. The latest update is always installed for devices below the minimum. Enforcement occurs at the specified time in each device’s local time zone. Select the **Minimum Version** from the dropdown. Devices that do not meet this requirement receive the update so they reach at least this version. Set the **Enforcement Deadline** (date and time) by which the minimum version must be met. Updates are cached and users can voluntarily update before this deadline. ### Related Articles Deploy pre-packaged applications across platforms Configure version enforcement, notifications, and install options for Auto Apps on macOS