> For clean Markdown of any page, append .md to the page URL.
> For a complete documentation index, see https://docs.merge.dev/merge-workforce/devices/llms.txt.
> For AI client integration (Claude Code, Cursor, etc.), connect to the MCP server at https://docs.merge.dev/_mcp/server.

# Devices

> Build once. Connect to every API, tool, and LLM. Ship products and agents to production without owning the integration stack.

## Docs

- [Workforce desktop client overview](https://docs.merge.dev/merge-workforce/devices/overview.md): What the Merge Workforce desktop client does, which of its modules you configure, how it identifies employees, and what it collects. Read this before deploying to your fleet.
- [Plan your deployment](https://docs.merge.dev/merge-workforce/devices/deployment-overview.md): What to prepare before pushing the Workforce desktop client, the full configuration key reference for macOS and Windows, and how to roll out in rings.
- [Deploy with Iru](https://docs.merge.dev/merge-workforce/devices/deploy/iru.md): Step-by-step Iru deployment of the Merge Workforce desktop client on macOS, plus what to do for Windows devices managed by Iru.
- [Deploy with Jamf Pro](https://docs.merge.dev/merge-workforce/devices/deploy/jamf.md): Step-by-step Jamf Pro deployment of the Merge Workforce desktop client, including the PPPC, system extension, and content filter payloads macOS requires.
- [Deploy with Microsoft Intune](https://docs.merge.dev/merge-workforce/devices/deploy/intune.md): Step-by-step Intune deployment of the Merge Workforce desktop client for both macOS and Windows, including the macOS permission profiles and the Windows install properties.
- [Deploy with Mosyle](https://docs.merge.dev/merge-workforce/devices/deploy/mosyle.md): Step-by-step Mosyle deployment of the Merge Workforce desktop client, including device group assignment and the macOS permission payloads it requires.
- [Deploy with Configuration Manager](https://docs.merge.dev/merge-workforce/devices/deploy/configuration-manager.md): Deploy the Merge Workforce desktop client to Windows with Microsoft Configuration Manager, passing your organization's values as MSI install properties.
- [Deploy with Workspace ONE](https://docs.merge.dev/merge-workforce/devices/deploy/workspace-one.md): Step-by-step Omnissa Workspace ONE UEM deployment of the Merge Workforce desktop client for macOS and Windows, including the macOS permission profiles and the Windows install properties.
- [Deploy with any other MDM](https://docs.merge.dev/merge-workforce/devices/deploy/other-mdm.md): What any MDM has to deliver to deploy the Merge Workforce desktop client on macOS or Windows: the package, the configuration values, and on macOS the four permission payloads.
- [Decommission a device](https://docs.merge.dev/merge-workforce/devices/deploy/decommission.md): How IT administrators take devices out of a Merge Workforce deployment through their MDM, for a few devices or the whole organization, and clean up local data.
- [Privacy and data collection](https://docs.merge.dev/merge-workforce/devices/privacy-and-data-collection.md): A complete reference of the data the Merge Workforce desktop client sends to Merge, the categories it is structurally incapable of collecting, and retention and residency controls. Written to be shared with security teams and works councils.
- [Employee FAQ](https://docs.merge.dev/merge-workforce/devices/employee-faq.md): A plain-language FAQ about the Merge Workforce desktop client, written for employees. Share it as-is or adapt it for your internal wiki.
- [Troubleshooting](https://docs.merge.dev/merge-workforce/devices/troubleshooting.md): How to diagnose the Merge Workforce desktop client when devices do not appear, identity does not resolve, users get prompted, or it conflicts with EDR and network clients.