How Configuration Policies Resolve: Default → Override

What's in the demo

• The rule: a policy can be assigned at five levels (partner, organization, site, device group, device), and when two policies set the same feature the closest level wins, decided feature by feature
• Create "Summit Baseline — All Clients" in the Partner library, so it belongs to the MSP rather than any one customer
• Set two features on it: a weekly maintenance window opening at 2:00 AM for 3 hours, Central time (America/Chicago), and warranty alerts that warn 90 days before expiry and go critical at 30
• Assign it with one checkbox: All organizations (partner-wide)
• Override one client: a second policy, "Acme — Night-Shift Maintenance", owned by Acme Manufacturing, with only a maintenance window (6:00 PM for 4 hours) and no warranty settings
• Assign the override at the organization level, and what the Priority field does (it only breaks ties at the same level; lower wins)
• The policy list: the baseline badged Partner-wide, the override badged with its organization
• An Acme workstation's Configuration tab: Maintenance Windows from the Acme override (Organization), Warranty still from Summit Baseline (Partner), Hardware Monitoring from Breeze Defaults
• The Inheritance Chain, closest level first, and the "Not enforced — using Breeze Defaults" list
• A workstation at another client still gets the partner baseline's 2:00 AM window

Questions this video answers

How does Breeze RMM decide which configuration policy applies to a device?

The closest assignment level wins: device, then device group, then site, then organization, then partner. It is decided feature by feature, so a more specific policy only replaces the features it actually configures.

What is the difference between a partner-wide assignment and an organization-level assignment in Breeze RMM?

A partner-wide assignment ("All organizations (partner-wide)") applies a Partner library policy to every client you manage, including clients you add later. An organization-level assignment applies a policy to one client and beats the partner-wide one for the features it sets, whatever priority either carries. Priority only breaks ties between policies at the same level, and the lower number wins.

Does an org override replace the whole partner policy?

No, only the features it sets. In the demo the Acme override sets just a maintenance window, so Acme devices take maintenance from the override and still get warranty alerts from the partner baseline.

What does "Not enforced — using Breeze Defaults" mean on a device?

The features listed there are not configured by any policy that reaches the device, so it falls back to Breeze's built-in defaults for them. Breeze lists them apart from the enforced features so you can tell what a policy set from what was never set.

How do I see where a device's setting came from in Breeze RMM?

Open the device and go to its Configuration tab. Effective Configuration shows each feature's winning policy and level ("From: [policy]", badged Organization, Partner, or Breeze Defaults), and the Inheritance Chain lists every policy that reaches the device, closest first, with its level and priority.