Converting legacy multi-platform policies to Android-only viewSolved

Participant
Discussion
5 months ago Jan 05, 2026

Hi everyone. I’ve noticed that with the newer Hexnode policy UI, we can easily create an Android-only policy by going to Policies > New Policy > Help me create policy > Android. This is a great feature that keeps the console clean.

However, we have several older policies created before this workflow existed, and they still display every single platform tab (iOS, macOS, Windows, etc.). Is there a way to edit one of these existing legacy policies and convert it to an Android-only view? I tried cloning them, but the clone still retains all the platform tabs.

I know the iOS or Windows settings won’t accidentally apply to our Android fleet, but it is incredibly easy for my team to accidentally make an edit under the wrong platform tab and waste time troubleshooting why the Android setting didn’t take effect. Is there a conversion trick I am missing here?

Replies (1)

Marked SolutionPending Review
Hexnode Expert
5 months ago Jan 05, 2026
Marked SolutionPending Review

Hello,

Thanks for reaching out to Hexnode Connect.

To answer your question directly: at present, older fully custom multi-platform policies cannot be converted, stripped down, or cloned into a single-platform Android-only view. Any policy created before the introduction of the new flow will permanently retain all platform tabs, even if cloned.

Your concern regarding administrative confusion is completely valid. While the Android devices will safely ignore configurations made under the iOS or Windows tabs, having those extra tabs visible increases the margin for human error during routine edits.

To resolve the UI clutter and prevent your team from editing the wrong tabs, the recommended approach is to transition to fresh policies.

  1. Navigate to Policies > New Policy > Help me create a new policy > Android to generate a clean, Android-only policy.
  2. Manually replicate your required Android configurations into this new policy.
  3. Associate the new Android-only policy with your target devices or device groups.
  4. Unassign and retire the older multi-platform policy.

While this requires a bit of upfront manual migration, it ensures your ongoing policy management remains streamlined and error-free for your administrators.

I hope this helps. If you find any more issues or need further assistance feel free to reach out.

Best regards,
George,
Hexnode UEM

Save