> ## Documentation Index
> Fetch the complete documentation index at: https://docs.inviolet.ai/llms.txt
> Use this file to discover all available pages before exploring further.

# VMware Workspace ONE

> Deploy the Inviolet extension via a Workspace ONE UEM Custom Settings profile — Windows OMA-URI and macOS plist variants.

Workspace ONE UEM Custom Settings profile. The Windows (OMA-URI) and macOS
(plist) variants ship in the same generated document.

<Note>
  Generate your profile first: **App → Settings → MDM → VMware Workspace ONE**
  downloads `inviolet-extension.ws1.xml` with your `org_id`, `enrollment_token`,
  and `config_signature` already substituted. See the
  [MDM overview](/guides/mdm/overview) for what the payload contains.
</Note>

## Prerequisites

* Workspace ONE UEM administrator access
* The generated `inviolet-extension.ws1.xml` from Settings → MDM
* A pilot smart group

<Note>
  Custom Settings profiles are **platform-scoped** — create one profile for
  Windows and a separate one for macOS if you manage a mixed fleet.
</Note>

## Windows

Create a **Custom Settings** profile with two OMA-URI entries from the generated
document:

* **`ExtensionInstallForcelist`** — force-installs the Inviolet extension (Edge).
* **`ExtensionSettings`** — the managed-config JSON carrying
  `org.inviolet.extension`.

## macOS

Create a **Custom Settings** profile and paste the embedded **plist payload**
from the generated document (the `com.google.Chrome.extensions.<id>` →
`org.inviolet.extension` dictionary).

## Assign + verify

Assign to a **pilot smart group**, then broaden. On a target device open
`chrome://policy/` or `edge://policy/` and confirm the force-install and
managed-config entries are present. The extension then enrolls into your tenant.

## Read next

* **[MDM overview](/guides/mdm/overview)** — the managed-config schema and identity modes
* **[Microsoft Intune](/guides/mdm/intune)** · **[Jamf Pro](/guides/mdm/jamf)** · **[Kandji](/guides/mdm/kandji)**