Deployment

macOS deployment

Deploy InputGuard to macOS devices with a deployment package from your organization’s deployment profile: install the configuration profile, then run the enrollment script.

Overview

macOS devices are deployed with a deployment package you download from the portal. Each package is a ZIP containing two artifacts plus a README:

  • A managed configuration profile (inputguard.mobileconfig) that carries your organization’s static configuration — and, in production, force-installs and locks the extension.
  • A generic enrollment script that gives the device a stable identity, captures hostname and OS, and writes the device-specific managed configuration.
  • A README with the exact steps for this platform.

The administrator workflow is the same on every platform: install the profile or policy, then run the enrollment script. The user never visits the Chrome Web Store or installs anything manually.

Organization deployment

InputGuard deployment packages install the extension and enroll devices for you. Users do not need to visit the Chrome Web Store or install the extension manually.

Deploying through MDM?

The configuration profile is exactly what MDM platforms consume — push it through Jamf, Microsoft Intune, Kandji, or Mosyle. See MDM deployment.

Download the package

Deployment packages are generated per organization from a deployment profile in the portal, so there is nothing to download here — you get the macOS package from your own workspace.

  1. 1

    Open Deployment in the InputGuard portal

    Go to the Deployment page in your workspace.
  2. 2

    Create or select a deployment profile

    A profile carries your organization’s enrollment settings and can be reused across devices.
  3. 3

    Open Deploy and download the package

    Open the profile’s actions (⋮) menu, choose Deploy…, then select Download deployment package under macOS. You get a ZIP with the configuration profile, the enrollment script (inputguard-enroll.sh), and a README.

Production vs. development packages

Production packages force-install the published Chrome Web Store extension and are enabled once your workspace is configured with the production extension ID. Until then the portal shows a publication notice, and only development packages (for the unpacked extension, in local dev) are offered.

Install on a device

Unzip the package on the macOS device, keeping both files together, then:

  1. 1

    Install the configuration profile

    Double-click inputguard.mobileconfig and approve it in System Settings, or push it through your MDM. In production it also force-installs and pins the extension.
  2. 2

    Run the enrollment script

    With both files in the same folder, run as root: sudo ./inputguard-enroll.sh. It creates (or reuses) a stable device identity, captures hostname and OS, and writes the device-specific managed configuration.
  3. 3

    Reload Chrome policy

    Restart Chrome (or open chrome://policy and click Reload policies) so the managed configuration takes effect.

Verify enrollment

After running the enrollment script, open the portal and go to the Devices page. The macOS device should appear in the device list, confirming it registered with your organization. Once it is listed, you can assign policy to it.

Not showing up?

Give enrollment a moment to complete, then refresh the Devices page. See Device enrollment for how registration works.