How inheritance works

For each rule, the first defined value wins:

Machine override → Site policy → Organization default

Offline timing, low-disk email, CPU, memory and service selections inherit independently. A CPU or memory override replaces the complete resource rule, not just the fields you changed. A service override replaces both platform lists and their stopped duration as one rule; it does not add names to inherited lists.

An organization is one isolated workspace. A site organizes machines within it. Do not treat a site label as a separate customer security boundary. Owners and operators can edit; viewers can inspect.

Make a shared change

  1. Open Policies and select the organization or site scope.
  2. Choose the rule to edit. Review its current source and effective values.
  3. Enter the intended settings and inspect the affected-machine preview.
  4. Save, then confirm the resulting rule source on a representative machine.

Machines shielded by a more specific override are not changed by a shared rule. A site policy can exist before any machine uses that site. New enrollments and later site moves use the applicable inherited rules.

Restore inheritance

In machine details, open Monitoring policy and use the inheritance control for the selected rule. Clearing an override means future shared changes apply again. An explicit override equal to today's default is still an override; it will not automatically follow tomorrow's default.

Before clearing all overrides, review each rule. The resource Configure buttons and offline bell can create machine overrides too.

Understand incident effects

Changing effective CPU/memory values closes the current resource incident and restarts timing. Removing a watched service closes that service incident; changing its stopped duration resets the window. A source change with identical effective values preserves the timer.

Offline notification timing is captured per incident, while muting immediately cancels pending offline mail. Low-disk email has its own switch. Maintenance does not change inheritance.

A stale preview is a reason to review

The editor checks an organization revision. If another edit, enrollment, site move or unenrollment changes the scope, an older save is rejected. Close the editor, refresh, reopen it and review the new impact before saving. Do not repeatedly submit an outdated preview.

Recent policy changes show actor, scope, rule and affected-machine count. Use that history when explaining an unexpected alert or exception.