--- title: "Deploy ControlUp for Apps on macOS" slug: "deploy-apps-on-macos" updated: 2026-07-23T10:27:40Z published: 2026-07-23T10:27:40Z canonical: "support.controlup.com/deploy-apps-on-macos" --- > ## Documentation Index > Fetch the complete documentation index at: https://support.controlup.com/llms.txt > Use this file to discover all available pages before exploring further. # Deploy ControlUp for Apps on macOS macOS Support Is in Beta macOS support for ControlUp for Apps is currently in Beta. To join the Beta program, contact your ControlUp representative. Before You Begin - The first time you open ControlUp for Apps, a setup wizard walks you through the deployment steps. Follow the instructions in the wizard or use this article to deploy ControlUp for Apps on macOS devices. - For Windows deployment instructions, see [Deploy ControlUp for Apps](/v1/docs/deploy-controlup-for-apps). ControlUp for Apps collects web application data from supported macOS devices using the following components: - **ControlUp for Apps module**: An add-on for the ControlUp for Desktops Agent that runs on the device. - **ControlUp for Apps browser extension**: Required for capturing web application usage and experience metrics from supported browsers. macOS deployment depends on how your Mac devices are managed. Use the unmanaged deployment path only for Mac devices that are not managed by Mobile Device Management (MDM). If the device is managed by an MDM solution, use the MDM-managed deployment path. ## Prerequisites Read [ControlUp for Apps Overview](/v1/docs/controlup-for-apps-overview) for general prerequisites. For macOS deployment, make sure that: - The macOS device has ControlUp for Desktops Agent version 2.18 or higher installed. - The macOS device can receive the supported ControlUp for Apps module version available for your tenant. - Employees access monitored applications with Google Chrome or Microsoft Edge. - For unmanaged Mac devices, the device can access the official Chrome and Edge web stores. - For MDM-managed Mac devices, you can deploy browser extension configuration profiles through your MDM tool, such as Jamf, Microsoft Intune, or Kandji. ## Deployment Instructions To access deployment settings, go to **Settings > Applications**. ![AccessApplicationsSettings.png](https://cdn.document360.io/098100b7-b9da-4bea-b4b9-017140ab863e/Images/Documentation/AccessApplicationsSettings.png) ### Deploy the ControlUp for Apps Module 1. Select the **Deployment** tab. 2. Add or edit a deployment rule. 3. Set **Platform** to **macOS**. 4. In **Version**, select the supported macOS version available for your tenant. 5. Select the target **device groups** or **device tags**. To learn how to create and manage them, see [Organize Devices with Groups and Tags](/v1/docs/organize-devices-with-groups-and-tags). 6. Click **Apply**. The selected version is installed on macOS devices that match the selected device groups or device tags. ### Deploy the Browser Extension Browser extension deployment for macOS depends on how your Mac devices are managed: - **[Unmanaged Mac Devices](/docs/deploy-apps-on-macos#unmanaged-mac-devices)**: Use this method only for Mac devices that are not managed by Mobile Device Management (MDM). - **[MDM-Managed Mac Devices](/docs/deploy-apps-on-macos#mdm-managed-mac-devices)**: Use your MDM tool to deploy the browser extension. #### Unmanaged Mac Devices 1. Select the **Extensions** tab. 2. Add or edit an extension deployment rule. 3. Set **Browser extension deployment** to **Automatically install via Web Store**. 4. Select the target device groups or device tags. 5. In **Browsers**, select **Google Chrome**, **Microsoft Edge**, or both. 6. Click **Apply**. 7. Ask users to log off and log back in for the extension to become operational. ControlUp deploys the browser extension from the official Chrome and Edge web stores. Local installation from the ControlUp CDN is not supported for macOS. If prompted by macOS or the browser, users must approve or enable the browser extension. #### MDM-Managed Mac Devices 1. Select the **Extensions** tab. 2. Add or edit an extension deployment rule for the relevant macOS devices. 3. Set **Browser extension deployment** to **Do not install**. 4. Select the target device groups or device tags. 5. Click **Apply**. 6. Deploy the required browser extension configuration profiles through your MDM tool. 7. Ask users to log off and log back in after the ControlUp for Apps module and browser extension configuration are deployed. Setting **Browser extension deployment** to **Do not install** prevents ControlUp from overriding the browser extension deployment managed by your MDM tool. The MDM configuration profiles force-install the ControlUp for Apps browser extension from the official browser web stores. Dynamic runtime settings are handled by the ControlUp for Apps module on the device. ## Post-Deployment Verification After users log back in, verify that the browser extension is communicating with the local ControlUp for Apps module. Open the extension UI from the browser. **Online** indicates that the browser extension is connected to the local module. ![Extension UI connected](https://cdn.document360.io/098100b7-b9da-4bea-b4b9-017140ab863e/Images/Documentation/ExtensionUiConnected(1).png) After employees access monitored App Groups from Google Chrome or Microsoft Edge, macOS data appears in ControlUp for Apps. ## Troubleshooting If macOS data does not appear in ControlUp for Apps, check the following: - The device matches the macOS deployment rule. - The ControlUp for Apps module is installed. - The browser extension deployment method matches the device management type: - For unmanaged Mac devices, **Browser extension deployment** is set to **Automatically install via Web Store**. - For MDM-managed Mac devices, **Browser extension deployment** is set to **Do not install**, and the extension is deployed through your MDM tool. - The correct browser is targeted in the extension deployment rule. - The user logged off and logged back in after deployment. - The browser extension UI shows **Online**. ### Enable Logs for Troubleshooting If you encounter deployment issues or communication errors, ControlUp Support might ask you to enable diagnostic logs. 1. Go to **Settings > Applications**. 2. Select the **Advanced** tab. 3. Under **Save logs**, select **Yes**. After logging is enabled, diagnostic logs are saved locally on the macOS device in the following folder: `/usr/local/com.controlup.edgedx.agent/Modules/appdx/logs` Copy the log files from this folder and provide them to ControlUp Support upon request. ### MDM Policy Verification For MDM-managed Mac devices, verify in your MDM tool that the browser extension configuration profile was deployed to the target devices. You can also verify that the browser received the extension policy: - In Google Chrome, open `chrome://policy`. - In Microsoft Edge, open `edge://policy`. If the extension is installed but does not communicate with the local module, contact ControlUp Support.