InputGuard

Getting Started

Deploy InputGuard to devices

Roll InputGuard out across a managed fleet by assigning the Chrome extension through your normal channel, then running per-OS enrollment scripts generated from your organization’s deployment profile.

Individual installation vs. organization deployment

These are two different paths. Individual users install InputGuard themselves; organizations deploy it to devices by assigning the extension centrally and running an enrollment script.

Individual users

Individuals install InputGuard directly from the Chrome Web Store.

  • No account required
  • No organization required
  • Local detection
  • Local audit history

Organization deployment

Each deployment script is designed to:

  • Configure device enrollment
  • Write InputGuard extension managed configuration
  • Connect the device to the organization

Organization deployment

Install or assign the InputGuard Chrome extension through your normal browser-management channel. InputGuard enrollment scripts then configure the installed extension and enroll devices into your organization.

How deployment works

From a deployment profile in the portal, open Deploy… and download a direct enrollment script for the operating system. On each device the admin installs or assigns the Chrome extension through their normal channel, then runs the script; together they:

  • Apply your organization’s static configuration — org, deployment key, and API endpoint.
  • Give the device a stable identity and capture its hostname and OS.
  • Connect the device to the organization so it appears in the portal.

The result is a hands-off flow for the end user:

  1. 1

    Admin assigns or installs the Chrome extension

    Use the Chrome Web Store, Google Admin, MDM, Group Policy, RMM, or existing Chrome policy.
  2. 2

    Admin runs the enrollment script

    Run it on the device, or push it through management tooling.
  3. 3

    Device enrolls into the organization

    The enrollment script establishes the device identity and connects it to your org.
  4. 4

    Device appears in the portal

    Confirm it on the Devices page, then assign policy.

Management platforms

Enrollment scripts distribute through Jamf, Microsoft Intune, Kandji, Mosyle, RMM, and similar tooling. See MDM deployment.

Choose your platform

The installation mechanics differ slightly per operating system. Follow the guide that matches your fleet:

Before you start

Deployment assumes you’ve already created an organization and a deployment profile. If you haven’t, start with Create an organization. For the concepts behind profiles, enrollment keys, and device registration, see Device enrollment.