WEBVTT

00:00:00.250 --> 00:00:06.220
Open Administration, Policies, Agent Policies. Built-in monitoring baselines apply by

00:00:06.220 --> 00:00:12.540
device class. More specific scopes override broader settings. Read the resolution order on

00:00:12.540 --> 00:00:18.791
this page before changing a threshold; otherwise a device-specific policy may explain why

00:00:18.791 --> 00:00:21.600
an organization-wide edit has no effect.

00:00:22.753 --> 00:00:28.729
The new custom policy starts as a clone of a built-in baseline. Type a descriptive name,

00:00:28.729 --> 00:00:34.500
choose the device class and select the intended customer. This example is preparation

00:00:34.500 --> 00:00:39.728
only: we leave the form unsaved and do not change monitoring on any endpoint.

00:00:40.924 --> 00:00:46.954
The table shows scope, device count and alert-to-ticket state. Open an existing baseline

00:00:46.954 --> 00:00:53.122
using Edit, then inspect its checks before planning changes. For a real rollout, save only

00:00:53.122 --> 00:00:59.222
reviewed settings, verify effective policy on a pilot device, and confirm later telemetry

00:00:59.222 --> 00:01:00.524
and alert behavior.
