How does Hexnode handle multiple overlapping policies on a single device?Solved

I think whichever policy you link last wins and just wipes out the older settings. We usually just delete the old policy completely before assigning a new one to avoid any issue. 

Ok thats interesting. I think the auto-lock is something a restriction so ideally the most restrictive one should get precedence, I’m not sure though.

Hello everyone, thanks for raising this. 

Hexnode UEM does not randomly overwrite or alternate settings when policies overlap. Instead, it uses programmatic logic to evaluate and merge configurations based on the specific payload type: 

• Most Restrictive Wins: For security and restriction payloads (e.g., passcodes, device restrictions), Hexnode UEM automatically enforces the most rigid parameter. If your policy allows a 5-minute auto-lock, but another policy restricts it to 2 minutes, Hexnode UEM will enforce the 2-minute limit.
• Merged Payloads: For distinct configurations (e.g., Wi-Fi networks, VPNs, web clips, apps), Hexnode UEM combines them, so all settings apply simultaneously to the device. 
• Last Applied Wins: For interface settings that can only support a single active state on the device (such as wallpapers or kiosk layouts), the configurations cannot be merged. In these cases, the policy that was most recently applied or updated in the portal takes absolute precedence.

To verify the final compiled state of a device, navigate to Manage > Devices and click on the specific device. From there, open the Policies sub-tab to view the finalized restrictions currently enforced on that device. 

For a deeper dive into managing overlapping payloads at scale, check out our guide on Global Policy Inheritance and Conflict Resolution. 

Regards, 
Simon Scott 
Hexnode UEM