Hi everyone,
We have multiple policies assigned across device groups and user groups in our setup. In some cases, I noticed that the same setting is configured differently across policies—for example, camera access is allowed in one policy but blocked in another.
I wanted to understand how Hexnode handles this. Which policy actually takes effect on the device when there’s a conflict like this?
14 Views
Yeah, we’ve seen similar situations. Especially with passcode policies and restrictions—it’s not always obvious which one wins unless you check the device state.
Would be good to know if there’s a defined priority or order.
This is a common scenario when devices are associated with multiple groups or users. In Hexnode UEM, policy conflicts are handled through a deterministic resolution mechanism to ensure the device ends up in a predictable state.
Here’s how it works:
If policies target different settings, they are applied together without any issue.
If multiple policies target the same setting, conflict resolution depends on the payload type:
For example:
If one policy allows the camera and another blocks it → the camera will be blocked
If one passcode requires 4 digits and another enforces alphanumeric → the stricter one is applied
To verify what’s actually applied on a device, you can check the Policy Summary section on the device details page. This will show the effective policy for each setting.
Don't have an account? Sign up
