---
title: Set up End User Device Monitoring
description: >-
  Set up End User Device Monitoring to collect performance and connectivity data
  from employee desktops and laptops.
breadcrumbs: >-
  Docs > Infrastructure > End User Device Monitoring > Set up End User Device
  Monitoring
---

> For the complete documentation index, see [llms.txt](https://docs.datadoghq.com/llms.txt).

# Set up End User Device Monitoring

Set up the Datadog Agent on employee desktops and laptops to collect [End User Device Monitoring data](https://docs.datadoghq.com/infrastructure/end_user_device_monitoring.md).

## Supported platforms{% #supported-platforms %}

- Windows 10 and later
- macOS 11 and later

## Permissions{% #permissions %}

The following permissions control access to End User Device Monitoring:

| Name                                                            | Description                                                                                   | Default role          |
| --------------------------------------------------------------- | --------------------------------------------------------------------------------------------- | --------------------- |
| End User Devices Read (`end_user_devices_read`)                 | View End User Device Monitoring, including the command center, summary, and devices explorer. | Datadog Standard Role |
| End User Devices Config Read (`end_user_devices_config_read`)   | View End User Device Monitoring organization settings.                                        | Datadog Admin Role    |
| End User Devices Config Write (`end_user_devices_config_write`) | Change End User Device Monitoring organization settings.                                      | Datadog Admin Role    |

The Datadog Standard Role includes End User Devices Read. The Datadog Admin Role includes all three permissions. If your organization uses [custom roles](https://docs.datadoghq.com/account_management/rbac/permissions.md#custom-roles), an admin with the User Access Manage permission needs to add these permissions to the roles that should use End User Device Monitoring. For details, see [Datadog Role Permissions](https://docs.datadoghq.com/account_management/rbac/permissions.md#end-user-device-monitoring).

End User Device Monitoring also uses permissions from other Datadog products for the full product to work.

Command Center requires **Work Items Read** (`cases_read`) and **Work Items Write** (`cases_write`).

Identity mapping requires **Reference Tables Read** (`reference_tables_read`) or **Reference Tables Write** (`reference_tables_write`), depending on the action. Access restrictions on the configured reference table also apply.

The following permissions apply to the corresponding feature, not to basic End User Device Monitoring access:

- Network Path data requires **Network Path Data Read** (`network_path_config_read`).
- Network-device and access-point information requires **NDM Read** (`ndm_devices_read`).
- Network connection data requires **Network Connections Read** (`network_connections_read`) when network-connection permission enforcement is enabled for the organization.

## Set up the Datadog Agent{% #set-up-the-datadog-agent %}

Follow the setup instructions for your platform:

- [macOS](https://docs.datadoghq.com/infrastructure/end_user_device_monitoring/setup/macos.md)
- [Windows](https://docs.datadoghq.com/infrastructure/end_user_device_monitoring/setup/windows.md)

## Next steps{% #next-steps %}

To collect additional data from monitored devices, enable one or more of the following features or integrations:

- [Live Processes](https://docs.datadoghq.com/infrastructure/process.md)
- [Logs](https://docs.datadoghq.com/logs.md)
- [Network Path](https://docs.datadoghq.com/network_monitoring/network_path/setup.md)
- [WiFi/WLAN integration](https://docs.datadoghq.com/integrations/wlan.md)
- [Windows Crash Detection integration](https://docs.datadoghq.com/integrations/wincrashdetect.md)
- [Windows Event Log](https://docs.datadoghq.com/integrations/event-viewer.md?tab=logs)

## Getting started{% #getting-started %}

Once devices start populating, start exploring End User Devices by:

1. **Mapping devices to end users with a Reference Table.** On the Settings page, click Edit to upload a mapping between device identifiers, such as hostname, and user attributes such as name, email, and team.
1. **Asking Bits about device health and trends.** Open [Bits Chat](https://docs.datadoghq.com/bits_ai/bits_chat.md) and ask questions about the fleet in natural language. For example, ask which devices are using the most CPU, which laptops have low battery capacity, or which users lost connectivity.
1. **Querying device data with the Datadog MCP Server.** Connect an AI client, such as Cursor or Claude, to the [Datadog MCP Server](https://docs.datadoghq.com/mcp_server.md) to retrieve device metrics, logs, and related telemetry through that client. See [Set up the Datadog MCP Server](https://docs.datadoghq.com/mcp_server/setup.md) to get started.
1. **Reviewing battery health.** Create a dashboard with [battery metrics](https://docs.datadoghq.com/integrations/battery.md#data-collected) such as maximum capacity, cycle count, and charge status to identify laptops to replace.
1. **Tracking latency to destinations.** Set up [Network Path](https://docs.datadoghq.com/network_monitoring/network_path/setup.md) on monitored devices to measure latency from a device to a destination, such as a SaaS application, and find the hop where delay is introduced. Read [Trace network paths from user devices to SaaS applications](https://docs.datadoghq.com/infrastructure/end_user_device_monitoring.md#trace-network-paths-from-user-devices-to-saas-applications) for examples.

## Further reading{% #further-reading %}

Additional helpful documentation, links, and articles:

- [End User Device Monitoring](https://docs.datadoghq.com/infrastructure/end_user_device_monitoring.md)